Integrations: API tokens, connected apps, calendars and overlays

Integrations connect WorshipPro with the tools you already use. Pick by what you need:

• put services in Google, Apple or Outlook calendars: a calendar link, no programmer needed,
• show lyrics over a live stream: the overlay in the desktop app,
• feed a website, a spreadsheet, n8n or Zapier: an API token,
• ask an AI assistant about your songs and plans: a connected app.

Everything here only reads data. Nothing from outside can change your church.

Tokens and connected apps are on Settings → General, Integrations tab. You need Church settings: Manage (Owner, Administrator), and your church must be verified: Church verification.

Calendars

Your personal calendar. Everyone can do this:

1. Planning → Calendar → Subscribe.
2. Click Create my calendar link.
3. Click Add to Google Calendar or Apple Calendar. For Outlook, use Copy link.

It shows your serving and church events. Change link replaces the link, and Turn off ends it.

A calendar for the whole church or a team. This takes Calendar: Manage:

1. Planning → Calendar → Rooms & resources, iCal feeds tab.
2. Type a Feed name and choose Whole church or Team.
3. Click + (Add feed), then Copy subscription link.

A Whole church link shows every event in the calendar. A Team link shows the services that team is rostered for. Revoke ends a link.

Keep two things in mind. A calendar link works without signing in, so anyone who has it can read those events. And sync goes one way: changes made in Google Calendar don't come back, and Google can take several hours to refresh.

Overlay for a live stream

The overlay lives in the desktop app, not in the browser: Settings → Streaming, section Stream overlay (OBS Browser Source). It runs on your computer and needs no token. Steps: Streaming: lower thirds for OBS, vMix and NDI.

API tokens

A token lets an outside tool read your church's data. Give it only to a tool you trust.

1. On the Integrations tab, click New token.
2. Type a Name, e.g. “Website”.
3. Under What the integration can read, tick Songs, Service plans, Teams and roster, Events or People (contact details).
4. In Expires after, choose 30, 90, 180 or 365 days.
5. Click Create token, then Copy, and keep the token somewhere safe. This is the only time you'll see it.
6. Click Done, the token is stored safely.

People (contact details) takes People: Manage, and you must tick I understand — I have a data processing agreement with the recipient. Sensitive data and notes never leave through a token.

A church can have 10 active tokens. In the token list:

• Rotate makes a new token with the same scopes, and you become its creator. The old one keeps working for the period you choose, up to 7 days, so you have time to swap it.
• Revoke cuts access at once. Tick the box if the token leaked.
• Recent calls shows what the token did in the last 90 days.

A token can never do more than the person who created it can do today. If that person gets a narrower role, you'll see Partly working: the creator now has a narrower role. If they leave, the status changes to Inactive: its creator no longer has access. Another administrator can fix that with Rotate.

Before a token expires, its creator and the church's owner get an email, 7 days ahead and again the day before.

AI assistant and connected apps

You can connect Claude or another assistant so it can answer questions about songs, plans, the roster and events.

1. In the AI assistant (MCP) card, turn on AI has access. It's off by default, and with it off no AI connection works, even a valid one.
2. Open How to connect an assistant. It has the server address and the steps.
3. In claude.ai, add a custom connector with that address and click Connect.
4. WorshipPro asks you to approve the connection. Choose the Church, tick what the app can read, and click Allow.

Only someone who manages church settings can approve this. The app gets read-only access to the church you chose, with no contact details, sensitive data, finances or forms.

The connection then appears under Connected apps. Revoke cuts it off at once. A church can have 20 connected apps. Other assistants can use New token for an AI assistant instead.

AI and your data lists exactly what an assistant can see.

Webhooks

Webhooks aren't available yet. You'll see the Webhooks section on the Integrations tab, but Add endpoint ends with the message “Secure secret storage is not configured on the server yet.” For now, a tool that needs fresh data can read it through an API token on a schedule.

For developers

Send whoever builds your integration to the WorshipPro API page. It covers the first call, scopes, limits, pagination and examples, plus the OpenAPI specification (JSON). A token allows 120 units a minute and 5,000 an hour. A token must never reach your visitors' browsers, so a website has to fetch data on its server, or use a calendar link instead.

What's next

• Church verification
• Streaming: lower thirds for OBS, vMix and NDI