Connecting other software
Connect other software with webhooks, email addresses, bots, API tokens and AI assistants.
There are five ways to connect other software. Pick the smallest one that does the job.
| You want to | Use | Set up by | Can it read? |
|---|---|---|---|
| Post into one chat from another tool | Incoming webhook | The chat’s leader | No |
| Post emails into one chat | Email address | The chat’s leader | No |
| Be told when things happen | Outgoing webhook on a bot | A church admin, then the chat’s leader | Yes |
| Read, post, react and upload from your own software | API token on a bot | A church admin, then the chat’s leader | Yes |
| Let an AI assistant read and post | AI assistant connected to a bot | A church admin, then the chat’s leader | Yes |
To build on the API, start with API tokens. Every request, and every event an outgoing webhook sends, is in the API reference.
Who can see what
Invite-only chats are hidden from church admins, and integrations keep it that way.
Whoever runs a bot can read whatever the bot can read, and so can any AI assistant connected to it. So a bot starts in no chats, and an admin can’t put one into an invite-only chat they aren’t in. Someone who can add people to that chat has to do it, and everyone in the chat can see the bot’s name at the top of the page, even where the member list is hidden.
Incoming webhooks and email addresses only post. They have no token and no way to read, so a chat’s leader can set one up without giving anyone access to the chat.
A bot is a Standard member of its church, but unlike a person it can’t find open chats: it sees only the chats it was added to, and the people in them where the chat allows that. It can’t message anyone directly, lead a chat, redeem an invite, or see the church directory.
Bots
A bot is a Standard member of your church that software acts as. Your own software can use one through the API, or an AI assistant can connect to one. Either way, it has its own name and its own chats, and it never acts as the person who set it up. Everyone using the same bot shares those, so use one bot for each job.
Create one under Settings → Developers, then add it to chats from Chat settings → Developers, choosing whether it can post or only read.
Deactivating a bot takes it out of every chat, revokes its tokens and stops its webhooks. What it already posted stays, under its name.