Skip to main content

Integrations

B1 plugs into the tools your team already uses. Connect Slack or Discord for staff notifications, automate workflows in Zapier or Make, or export data on demand to Google Sheets — without paying for a separate integration platform and without ChurchApps hosting anything extra. Every integration runs on the third party's own infrastructure and talks to your church through B1's webhooks or REST API.

What's Available​

IntegrationWhat it doesDirectionEffort to set up
SlackPost readable notifications (new people, donations, sign-ups, …) to a Slack channelB1 → Slack2 minutes
DiscordSame, in a Discord channelB1 → Discord2 minutes
ZapierUse B1 events as triggers and B1 actions in any of Zapier's 7,000+ apps (waiting on Zapier's approval)Both5–10 min per Zap
MakeSame idea as Zapier, in Make's visual scenario builder (not released yet)Both5–10 min per scenario
Google SheetsExport People / Donations / Groups / Attendance to a spreadsheet on demand (not released yet)B1 → Sheet5 minutes
ClaudeAsk Anthropic's Claude questions about your church data, scoped to your permissions — free to try, recommendedBothUnder 3 minutes
ChatGPTSame idea with OpenAI's ChatGPT (needs a paid ChatGPT plan)Both10 minutes
MailchimpKeep a Mailchimp audience in sync with your people, groups, and saved lists — built into B1B1 → Mailchimp5 minutes
Connected servicesCurated recipes for Donorbox, Subsplash, VOMO, Clearstream, Text In Church, Mobile Message, CheckrVaries5–10 min each

How to Pick​

  • Just want a notification in chat? Use Slack or Discord — no third-party account, no Zap to maintain. Configured entirely inside B1Admin.
  • Want to automate something across apps (e.g. "when someone gives, add them to my Mailchimp list and Slack #donations")? Use Zapier or Make. Zapier is friendlier; Make is cheaper at scale and has more flexible logic.
  • Need a one-off data pull or a scheduled report? Use Google Sheets — paste an API key into the add-on's sidebar and click Export.
  • Want to ask questions in plain English ("how many first-time visitors last Sunday?", "summarize giving this month")? Start with Claude — it's free to try and sets up in less than 3 minutes. ChatGPT works too with a paid plan. Claude connects by signing in with your B1 account; ChatGPT uses a B1 API key.
  • Building your own custom integration? None of the above — talk to the REST API directly with an API key, or subscribe a server you control to webhooks.

What They Have In Common​

Everything is set up in B1Admin under Settings → Developer, which has three tabs: API Keys, Webhooks, and Connected Apps.

  • Slack, Discord, and Mailchimp are webhooks you create yourself on the Webhooks tab (pick the matching Connector Type). They don't need an API key.

  • Claude (signing in with your B1 account) shows up on the Connected Apps tab, where you can revoke it.

  • Zapier, Make, Google Sheets, ChatGPT, and Claude with a key authenticate with a B1 API key, created on the API Keys tab. The key:

    • Is bound to the person who created it and inherits that person's permissions
    • Can be narrowed with scopes — for example a Google Sheets export only needs people:read, not settings:write
    • Can be deleted at any time, instantly cutting the integration's access without affecting anything else

A few connectors (Zapier, Make) also register a webhook on your behalf when the Zap or scenario is turned on, and remove it when you turn the Zap off — you don't manage the webhook URL yourself.

tip

For Zapier and Make to register webhooks automatically, the API key needs the settings:write scope (plus the resource scopes for whatever the integration touches). A read-only key works for actions and exports but not for triggers.

Cost​

ChurchApps is free and open-source. Slack/Discord, the @churchapps/integration-sdk, and the official Zapier / Make / Google Sheets connectors are also free from our side. The third parties may charge for their own platforms (Zapier and Make both have generous free tiers; Slack, Discord, and Google Sheets are free for this purpose).

Building Your Own​

If none of the above fits, every B1 surface is open:

  • REST API — call B1 from any language with an Authorization: Bearer cak_… header
  • Webhooks — subscribe a public HTTPS endpoint to one or more event types and receive signed JSON payloads
  • OAuth + Connected Apps — if you're building a SaaS product used by many churches

Next Steps​

  • Slack & Discord — post chat notifications
  • Zapier — connect to 7,000+ apps
  • Make — visual workflow automation
  • Google Sheets — export to spreadsheets
  • Claude — ask Anthropic's Claude about your church data
  • ChatGPT — ask OpenAI's ChatGPT about your church data
  • Connected services — per-service recipes (Mailchimp, Donorbox, Clearstream, …)