All connectors
Implemented
Church management & ministry

ChurchSuite

Read ChurchSuite account profile details for authorised church-management integrations.

Read ChurchSuite account profile details for authorised church-management integrations.

Source actions

1

Destination actions

0

Data types

1

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

account
  • Get church account profile
    Source

    Read account name, timezone and currency. Contacts, children, giving and ministry records are not included.

    account.get

Authentication

ChurchSuite v2 OAuth access token with profile.read

Plans and access

ChurchSuite account with API v2 enabled for the authorised user/application. The token must have profile.read and access to the account. Core v2 authorisation is separate from public Embed feeds.

Test environment

Arrange an approved test account with ChurchSuite; no Nexra provider-backed validation recorded.

Rate limits

Provider account quotas apply; HTTP 429 uses bounded retries and Retry-After when supplied.

Pagination

Account profile is a single data object.

Provider events

Not included in this read-only batch. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Fixture-tested implementation only; provider sandbox and authorised-account validation have not run.
  • Only the listed reads are implemented. Writes, consent flows and automatic access-token refresh are not included.

Developer reference

  1. Create the ChurchSuite credentials described above with the narrowest permissions your flows need.
  2. 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
  3. 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.