Step 1: Manage Your Websites

Read before continuing...

Do you use the Next Steps Launcher on your church website and are looking to install your PrayerFlow there? If so, click here.

This article is specifically for installing your PrayerFlow on a site that does not already have the Launcher installed. If you have the Launcher installed and follow this guide for the same website, your PrayerFlow will not load.

Now back to our regular programming 📺

------------

While we recommend adding your PrayerFlow as an action step in the Next Steps Launcher, from time to time it might be helpful to install your PrayerFlow on a website that doesn't have the Launcher installed.

There are three steps to install your PrayerFlow to your website. Let's explore the first step.


Add your website URL(s)

You can install a PrayerFlow on as many websites as you'd like, as long as they don't have the Next Steps Launcher already installed on it. To whitelist the website(s) you're adding your PrayerFlow to (meaning that particular website is safe to show your PrayerFlow to load on)...

1. Make your way to your Prayer app and select PrayerFlow.

2. Select Share in the sidebar and click on Advanced Install.

3. Click the + Add New button to add a website URL you want your PrayerFlow to load on. The best way to do this is to go to the website and copy exactly what is shown in your browser's address bar. Then paste it in the field provided in your Nucleus Dashboard.


Note: 
  • Make sure that your URL includes the appropriate http:// or https:// in front of the web address. If you don't include that, your Flow will not show up on your website, even if you have it installed properly in your website's settings.


4. Click the Add URL button.

5. Repeat if you have more than one URL you'd like your PrayerFlow to load on.


What next?

While the next area on this page is the installation code to add to your website, we recommend checking over your PrayerFlow's button design settings first.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.