Connect Your Post Collections To Zapier

We get it – you're using a bunch of tools to keep all of your church records straight. To lower the chaos of your church communications, Nucleus now integrates with Zapier so that you can manage your subscriber data the way you want. Want new subscribers to flow straight into your Google Sheet, Mailchimp list, Slack channel, or other ChMS? With the Zapier integration, Nucleus can send subscriber data from your Post collections to Zapier the moment someone signs up — and from there, your Zap handles the rest.

Here's what we'll cover. Click any topic to jump ahead.

How It Works

When someone subscribes to a Post Collection on your Nucleus website, Nucleus can send their details to Zapier as a New Subscriber event. From there, your Zap routes that data wherever you need it — another app, a spreadsheet, a notification, or anything else Zapier supports. There are currently over 9,000 apps that Zapier talks to, so the world really is your oyster now.

Everything that happens after Nucleus delivers the event is handled by your Zap. Nucleus just sends the notification.

Note: This is a notification integration, not a full sync. Only new subscriptions that happen after your Zap is live will be sent to Zapier. Existing subscribers are not backfilled.

Before You Get Started

A few things need to be in place before new subscribers will reach Zapier:

  • The church-level Zapier integration is connected and enabled in Nucleus. You can check this under Settings > Integrations.
  • At least one Zap is turned on in Zapier, with Nucleus set as the trigger and New Subscriber as the event — and it has successfully registered with Nucleus. You'll know this is working when the integration detail page in Nucleus shows New Subscriber as Listening.
  • The Collection's Zapier setting is set to Yes (Default). More on that below.

If any of these are missing, subscribers will still work normally inside Nucleus — they just won't be sent to Zapier.

Connect Nucleus to Zapier

Setup moves back and forth between Nucleus and Zapier a couple of times. Here's the full flow:

  1. Start in Nucleus. Go to Settings > Integrations and tap Connect on the Zapier card. This opens the Zapier integration detail screen with setup instructions.
  2. Create a Zap in Zapier. On zapier.com, create a new Zap and set the trigger app to Nucleus. Choose New Subscriber as the trigger event.
  3. Authorize Nucleus from Zapier. When Zapier asks you to connect your account, it'll open a Nucleus sign-in screen. Sign in, select your church, and tap Allow and Continue to authorize Zapier to receive subscriber and campaign data. Zapier will then finish linking the connection on its side and send you back to Zapier.
  4. Finish and publish your Zap. Map the subscriber fields to whatever app comes next in your Zap (a Google Sheet row, a Mailchimp subscriber, ChMS, etc.), test if you'd like, then turn the Zap on. Once it's on and listening, the integration status in Nucleus will update to show Connected.
  5. Choose which Collections to include. In each Post Collection's settings, you can decide whether that collection should send subscribers to Zapier.

Choose Which Collections Participate

Each Post Collection has its own Zapier setting. To find it, go to Posts > Your Collection > Settings and look for the Subscriber Settings section.

If Zapier is connected at the church level, you'll see a Zapier (Connected) card with two options:

  • Yes (Default) — new subscribers for this Collection are sent to Zapier.
  • No (Don't Send) — people can still subscribe in Nucleus, but this Collection's subscribers won't be sent to Zapier.

What Zapier Receives

When Nucleus sends a New Subscriber event, Zapier exposes the following fields for you to map into your Zap:

About the subscriber:

  • First name
  • Last name
  • Email address
  • Unique subscriber ID

About the collection:

  • Campaign display name (the friendly title)
  • Campaign internal name
  • Unique campaign ID

A Few Things to Know

All active Zaps share the same church feed. If your church has multiple Zaps connected to Nucleus, every active Zap will receive events for any Collection where sending is enabled. There's no way to route Collection A to one Zap and Collection B to another from within Nucleus. If you need to split data between Zaps, use Zapier-side filters after receipt (available on some Zapier plans).

Disabling Zapier in Nucleus doesn't affect your subscribers. Turning off the Zapier integration pauses all Zap deliveries, but everyone stays subscribed in Nucleus. Collections, Campaigns, and emails all continue working as normal. Re-enabling the integration (or turning a Zap back on in Zapier) resumes the push.

Turning a Zap back on in Zapier can re-enable the integration. If the Nucleus integration was disabled, turning a Zap back on in Zapier can automatically re-register the connection — so you're not stuck manually flipping a switch in Nucleus every time.

You can run multiple Zaps. Multiple Zaps can be connected to the same Nucleus church integration at once. All active Zap listeners will receive eligible subscriber events.

Check the integration detail page if something seems off. Under Settings > Integrations > Zapier > Manage, you'll see whether the New Subscriber trigger is Listening (active webhooks registered) or Inactive (no Zaps are turned on). If it shows Inactive, head to Zapier and make sure your Zap is enabled.

What's Next?

Once your Zap is live, every new subscriber to your enabled Post Collections will flow automatically into whatever tools you've connected. Build as many Zaps as you need — and use Nucleus's collection-level settings to control exactly which Collections participate.

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