Integrations
Delivery into the tools your staff already use.
Engine is where the work is decided and assigned. When a piece is assigned, Engine posts to the chat tool the church connects and sends an email, and each person's pieces appear in the calendar they subscribe to. No one is asked to use a new inbox.
Where Engine posts
Where it posts
One chat tool per church. In Slack each person gets a direct message. Everyone gets an email in every case, so a church that connects nothing is still notified.
Slack
The biggest single answer when we asked, and the one churches most often leave. Free plans keep 90 days. Added once with a button, and then each person on the team gets their own message rather than a channel post.
Google Chat
Free with Google for Nonprofits, and where most of the churches leaving Slack said they went.
Microsoft Teams
For churches already on Microsoft 365. Engine uses the Workflows webhook, since Microsoft retired the old connectors in May 2026.
Anything else
One address covers Trello, Notion, Basecamp, BAND, NiftyPM, or Zapier in front of whatever you run. If it takes an incoming webhook, Engine can post to it.
Engine writes messages and reads none. It sends nothing to a member of the church. The one other system it writes into is below, and a staff member ticks a box for each write.
The calendar
The calendar feed
Each person subscribes once to a feed of their own pieces. It updates itself and needs no account linking: it is a read-only feed, not a write into the calendar.
Your list
The church's list
A follow-up path can add a guest to a list the church already runs. Engine writes the name and the address into that audience or list only when a staff member ticks the step, and the platform sends its own confirmation. Engine sends the guest nothing.
Mailchimp
Pick which audience each follow-up path adds people to. Mailchimp sends its own confirmation email, so no one is subscribed until they say so, and Engine never sends a thing.
Clearstream
Pick which list each follow-up path adds people to. Clearstream texts them to confirm before anything else reaches them, and Engine never sends a thing.
This is the only system Engine writes into. A person who has asked the church not to contact them is never added, and no one is subscribed until they confirm with the platform themselves.
Your money
The money file
Export from whatever the church keeps its books in and drop the file in. Engine counts it against the budgets and shows what it read before it writes anything.
What came in
What went out
Engine reads and counts. It writes nothing back into the accounting system, moves no money, and keeps no giver's name: gifts are summed into months on the way in.
Alongside
What a church runs
Engine does not replace a church management system, a giving platform or a website. Recording what the church runs stops setup from asking about it twice.
Church system
Giving and accounting
Team messaging
Boards and docs
Email and texting
Everything else
A system not on the list works if it accepts an incoming webhook. The list is extended as churches report what they run.
Set your church up
A connection is a pasted address during setup, about a minute each.