Data & Storage · Integration
ChMeetings
Add ChMeetings to your product for your customers, and give your AI agents governed access to it.
ChMeetings is church management software, and no catalogue category fits it exactly, so it sits here on the basis that its API is essentially a people and giving record store with custom fields rather than a CRM with opportunities. The developer API lives at api.chmeetings.com under an /api/v1/ prefix and covers people and their profile details, groups, contributions, pledges, campaigns, events and attendance. Paths are case-sensitive and use capitalised resource names such as /api/v1/People, so a lowercase path returns 404 rather than 401 and looks like a dead API. The key is generated once per organisation under Settings then Integrations then API Integration, and it grants access to the whole account with no scoping, so it should never be handed to an end user. Contributions are the only resource that is genuinely bidirectional, with people and group data intended mainly for reading out. fastn holds each organisation's key server side, keeps the case-sensitive paths correct, and maintains the connection as ChMeetings extends the API.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own ChMeetings account so their member records populate your product without a spreadsheet import.
Push contributions collected through your payment flow back into ChMeetings against the right person.
Read groups and attendance to drive engagement reporting inside your app.
Reconcile pledges against campaigns so a customer can see progress without leaving your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent record a contribution against a named person and campaign, with the amount, the person and the tenant written to a per-tenant audit log.
Have an agent report attendance trends for a group over a period and flag members who have stopped attending.
Let an agent compare pledges against received contributions for a campaign and summarise the shortfall.
Example prompt
How much of our building campaign pledge total has actually been received in ChMeetings so far?
Set up ChMeetings in 4 steps
- 01Enable the ChMeetings connector from your fastn dashboard.
- 02Have each customer authorise their own ChMeetings account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the ChMeetings integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a ChMeetings integration without building it. Your customers connect their own ChMeetings account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a ChMeetings update is not your on-call problem.
- One integration serves your product and your agents. The same governed ChMeetings connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
Airtable
PostgreSQLOften used alongside
Tools the same teams tend to run next to ChMeetings, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceChMeetings integration FAQ
How do I add a ChMeetings integration to my product?
Enable the ChMeetings connector in your fastn dashboard, then let each customer authenticate their own ChMeetings account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no ChMeetings client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own ChMeetings account?
Yes. Every connection is scoped to the individual customer, so each authorises their own ChMeetings account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this ChMeetings integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent record a contribution against a named person and campaign, with the amount, the person and the tenant written to a per-tenant audit log.
Who maintains the ChMeetings integration?
fastn does. When ChMeetings changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the ChMeetings integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large ChMeetings reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the ChMeetings integration?
A common starting point: let a customer connect their own ChMeetings account so their member records populate your product without a spreadsheet import. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the ChMeetings integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding ChMeetings does not change your per-connector cost. You can start free with 3 connected accounts.
Add ChMeetings to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.