ChurchSuite
Connect ChurchSuite to the rest of your business, with the right person approving what changes and a record of every action.
18 ways to read, 3 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with ChurchSuite, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Add contact note
contact_notes.createApproval by rule - Add event note
event_notes.createApproval by rule - List contact notes
contact_notes.listRead
Example flow
- ChurchSuite · List contact notes
contact_notes.listDone - ChurchSuite · Add contact note
contact_notes.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches ChurchSuite.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to ChurchSuite
- ChurchSuite's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
ChurchSuite contacts by ID, small groups and attendance, rotas, calendar events and notes for church-management integrations, without messaging or giving.
ChurchSuite API docs- Source actions
- 18
- Destination actions
- 3
- Data types
- 15
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
account1
- Get church account profileSource
Read account name, timezone and currency. Contacts, children, giving and ministry records are not included.
contact notes2
- Add contact noteDestinationNot retried automaticallyApproval before production
Record a note against one contact. No message is sent.
- List contact notesSource
Read notes recorded against one contact.
contacts1
- Get contactSource
Read one Address Book contact by ID, including communication consent flags.
event notes2
- Add event noteDestinationNot retried automaticallyApproval before production
Record a note against one event. No message is sent.
- List event notesSource
Read notes recorded against one event.
events2
- Get calendar eventSource
Read one calendar event.
- List calendar eventsSource
Read calendar events in a date window.
ministries2
- Get rota ministrySource
Read one rota ministry.
- List rota ministriesSource
Read rota ministries and their rotation settings.
ministry members1
- List ministry membersSource
Read who serves in each ministry and team, with role IDs.
ministry teams1
- List ministry teamsSource
Read the teams within rota ministries.
rota roles1
- List rota rolesSource
Read rota roles, optionally for one ministry.
rota unavailability1
- List rota unavailabilitySource
Read periods when people are unavailable to serve.
small group attendances1
- List small group attendanceSource
Read attendance records for small group meetings.
small group clusters1
- List small group clustersSource
Read clusters that organise small groups.
small group members1
- List small group membersSource
Read group memberships with the member's contact or child ID and roles.
small group notes2
- Add small group noteDestinationNot retried automaticallyApproval before production
Record a note against one small group. No message is sent.
- List small group notesSource
Read notes recorded against one small group.
small groups2
- Get small groupSource
Read one small group.
- List small groupsSource
Read small groups with schedule and cluster.
Access and limits
- Authentication
- ChurchSuite v2 OAuth access token
- Plans and access
- ChurchSuite account with API v2 enabled for the authorised user/application. The token needs profile.read plus addressbook, smallgroups, rotas and calendar read scopes for the operations in use, and the matching write scope only for notes. Core v2 authorisation is separate from public Embed feeds.
- Test environment
- Arrange an approved test account with ChurchSuite.
- Rate limits
- ChurchSuite applies per-account API limits; HTTP 429 uses bounded retries and Retry-After when supplied.
- Pagination
- List endpoints use page and per_page (maximum 250) with pagination.next_page.
- Provider events
- ChurchSuite API v2 does not document outbound webhooks for these modules. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Contacts are read by ID only. Listing or searching contacts by name, email or phone is not offered so personal data never appears in a URL.
- Excluded: emails, SMS and other communications, giving, donations and payments, bookings, children's records, contact creation or edits, and every delete.
- Writes are limited to adding notes to contacts, small groups and calendar events.
- Access tokens from the client-credentials flow expire and are not refreshed automatically; replace the stored token when it expires.
- Filters that ChurchSuite accepts as arrays (for example group_ids[]) take one ID per request in this recipe.
Developer reference
- Create the ChurchSuite credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose ChurchSuite, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/churchsuite and the Connections API.