> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/planning-center.md).

# Planning Center

Work with people, giving, calendar events and check-in records in Planning Center, the church management suite.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector                               | Authentication |
| --------------------------------------- | -------------- |
| Planning Center (Personal Access Token) | Secret         |

#### Planning Center (Personal Access Token)

Connect to Planning Center People, Giving, Calendar and Check-Ins with a Personal Access Token.

**Set up in Planning Center**

1. Sign in to the Planning Center developer account for the user and organization whose data you need.
2. Create a Personal Access Token in the developer account. Retain the application ID and secret issued with the token.
3. Confirm that the user has access to the Planning Center products and records used by the workflow.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Planning Center (Personal Access Token)**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field  | Required | What to enter                                                                                                                                                                                                                                |
| -------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Application ID | Yes      | Create a free Personal Access Token at <https://api.planningcenteronline.com/personal\\_access\\_tokens>. Self-serve, no approval needed. [Provider instructions](https://api.planningcenteronline.com/personal_access_tokens).              |
| Secret         | Yes      | The secret paired with your Application ID, shown once when the token is created at <https://api.planningcenteronline.com/personal\\_access\\_tokens>. [Provider instructions](https://api.planningcenteronline.com/personal_access_tokens). |

**Provider documentation:** [Setup reference](https://developer.planning.center/docs/).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **Planning Center** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Create Person

Add someone to your Planning Center People directory, with their email, phone number and mailing address.

**Required permissions:** `people`.

**Inputs**

| Field                | Type            | Required | Description                                                                                                                   |
| -------------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- |
| First name           | string          | Yes      | The person's first name.                                                                                                      |
| Last name            | string          | Yes      | The person's last name.                                                                                                       |
| Email address        | string          | No       | Email address to save on the new profile. Saved as their primary email.                                                       |
| Phone number         | string          | No       | Phone number to save on the new profile. Saved as their primary number.                                                       |
| Birthdate            | date            | No       | Date of birth, used for birthday lists and children's ministry age grouping.                                                  |
| Campus               | select (string) | No       | Which campus this person belongs to. Only relevant for multi-campus churches. Options load from the selected connection.      |
| Status               | select (string) | No       | Whether the profile is active in the directory, or archived as inactive. Available values: Active, Inactive. Default: active. |
| Show advanced fields | boolean         | No       | Reveal membership, nickname, gender and mailing address fields. Default: false.                                               |
| Membership           | string          | No       | The membership label your church uses, for example Member, Regular Attender or Visitor.                                       |
| Nickname             | string          | No       | The name this person actually goes by, if it differs from their first name.                                                   |
| Gender               | string          | No       | Gender as your church records it. Planning Center accepts free text here.                                                     |
| Street address       | string          | No       | Street address. Fill the address fields together to save a mailing address.                                                   |
| City                 | string          | No       | City for the mailing address.                                                                                                 |
| State or region      | string          | No       | State, province or region for the mailing address.                                                                            |
| Postal code          | string          | No       | ZIP or postal code for the mailing address.                                                                                   |

**Outputs**

| Field              | Type    | Description                                                  |
| ------------------ | ------- | ------------------------------------------------------------ |
| Person ID          | string  | Planning Center id of the new profile.                       |
| Full name          | string  | Name as Planning Center formatted it.                        |
| Status             | string  | Whether the new profile is active or inactive.               |
| Created at         | string  | When the profile was created.                                |
| Email saved        | boolean | Whether the email address was attached to the new profile.   |
| Phone number saved | boolean | Whether the phone number was attached to the new profile.    |
| Address saved      | boolean | Whether the mailing address was attached to the new profile. |

#### List People

Search your Planning Center directory by name, email or phone, and get back matching profiles with their contact details.

**Required permissions:** `people`.

**Inputs**

| Field                 | Type            | Required | Description                                                                              |
| --------------------- | --------------- | -------- | ---------------------------------------------------------------------------------------- |
| Search                | string          | No       | Name, email address or phone number to search for. Partial matches work.                 |
| Maximum results       | integer         | No       | How many people to return. Higher values take longer. Minimum: 1.                        |
| Show advanced filters | boolean         | No       | Reveal filters for status, campus, updated-since, and resuming a search. Default: false. |
| Status                | select (string) | No       | Limit results to active or inactive profiles. Available values: Active, Inactive.        |
| Campus                | select (string) | No       | Only return people at this campus. Options load from the selected connection.            |
| Updated since         | datetime        | No       | Only return profiles changed on or after this moment. Useful for incremental syncs.      |
| Continue from         | string          | No       | Continue a previous search. Paste the value this action returned as next\_offset.        |

**Outputs**

| Field         | Type          | Description                                                                              |
| ------------- | ------------- | ---------------------------------------------------------------------------------------- |
| People        | object\_array | Matching profiles with their primary contact details.                                    |
| Total matches | integer       | How many profiles match, across all pages.                                               |
| Next offset   | string        | Pass back as Continue from to fetch the next page. Empty when there are no more results. |

#### Get Person

Look up one person's full profile, including every email address, phone number and mailing address on file.

**Required permissions:** `people`.

**Inputs**

| Field     | Type   | Required | Description                                      |
| --------- | ------ | -------- | ------------------------------------------------ |
| Person ID | string | Yes      | The Planning Center id of the person to look up. |

**Outputs**

| Field           | Type          | Description                                    |
| --------------- | ------------- | ---------------------------------------------- |
| Person ID       | string        | Planning Center id of the profile.             |
| Full name       | string        | Name as Planning Center formatted it.          |
| First name      | string        | Given name.                                    |
| Last name       | string        | Family name.                                   |
| Status          | string        | Whether the profile is active or inactive.     |
| Birthdate       | string        | Date of birth, when recorded.                  |
| Membership      | string        | The church's membership label for this person. |
| Campus          | string        | Campus this person belongs to.                 |
| Email addresses | object\_array | Every email address on the profile.            |
| Phone numbers   | object\_array | Every phone number on the profile.             |
| Addresses       | object\_array | Every mailing address on the profile.          |
| Updated at      | string        | When the profile last changed.                 |

#### Update Person

Change details on an existing Planning Center profile, such as their membership, campus or status.

**Required permissions:** `people`.

**Inputs**

| Field                | Type            | Required | Description                                                                            |
| -------------------- | --------------- | -------- | -------------------------------------------------------------------------------------- |
| Person ID            | string          | Yes      | The Planning Center id of the person to update.                                        |
| First name           | string          | No       | New first name. Leave blank to keep the current one.                                   |
| Last name            | string          | No       | New last name. Leave blank to keep the current one.                                    |
| Status               | select (string) | No       | Archive the profile as inactive, or reactivate it. Available values: Active, Inactive. |
| Membership           | string          | No       | New membership label, for example Member or Regular Attender.                          |
| Campus               | select (string) | No       | Move this person to a different campus. Options load from the selected connection.     |
| Show advanced fields | boolean         | No       | Reveal birthdate, nickname and gender fields. Default: false.                          |
| Birthdate            | date            | No       | New date of birth.                                                                     |
| Nickname             | string          | No       | The name this person goes by.                                                          |
| Gender               | string          | No       | Gender as your church records it.                                                      |

**Outputs**

| Field      | Type   | Description                                |
| ---------- | ------ | ------------------------------------------ |
| Person ID  | string | Planning Center id of the updated profile. |
| Full name  | string | Name after the update.                     |
| Status     | string | Directory status after the update.         |
| Updated at | string | When the change was applied.               |

#### Create Donation

Record a gift in Planning Center Giving against a fund, optionally crediting it to a person.

**Required permissions:** `giving`.

**Inputs**

| Field                  | Type            | Required | Description                                                                                                                                                  |
| ---------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Amount                 | number          | Yes      | Gift amount in dollars, for example 20.00.                                                                                                                   |
| Fund                   | select (string) | Yes      | Which fund the gift goes to, for example General or Missions. Options load from the selected connection.                                                     |
| Payment method         | select (string) | Yes      | How the gift was given. Available values: Cash, Check, ACH, Card.                                                                                            |
| Donor                  | string          | No       | The Planning Center profile to credit for this gift. Leave blank for an anonymous gift.                                                                      |
| Received on            | date            | No       | The date the gift was received. Omit to use Planning Center's current date and time.                                                                         |
| Show advanced fields   | boolean         | No       | Reveal check number, card details, payment source, batch and commit options. Default: false.                                                                 |
| Check number           | integer         | No       | Number printed on the check. Only applies to check gifts.                                                                                                    |
| Card or account last 4 | string          | No       | Last four digits of the card or bank account, so admins can reconcile the gift.                                                                              |
| Payment source         | select (string) | No       | Which system this gift came from. Leave blank to file it under a Stack AI source that is created once and reused. Options load from the selected connection. |
| Batch                  | select (string) | No       | An existing uncommitted batch to add this gift to. Leave blank to start a new batch. Options load from the selected connection.                              |
| Batch description      | string          | No       | Label for the new batch, so admins can tell it apart from ones they made themselves.                                                                         |
| Commit batch           | boolean         | No       | Finalise the batch so the gift appears in the donor's online giving history. Leave off to stage it for an admin to review. Default: false.                   |

**Outputs**

| Field                  | Type    | Description                                                            |
| ---------------------- | ------- | ---------------------------------------------------------------------- |
| Donation ID            | string  | Planning Center id of the recorded gift.                               |
| Amount                 | number  | Amount recorded, in dollars.                                           |
| Amount in cents        | integer | Amount recorded, in cents, exactly as Planning Center stores it.       |
| Currency               | string  | Currency of the gift.                                                  |
| Fund                   | string  | Fund the gift was designated to.                                       |
| Payment method         | string  | How the gift was given.                                                |
| Received on            | string  | Date the gift was received.                                            |
| Donor                  | string  | Profile credited for the gift, if any.                                 |
| Batch ID               | string  | Batch the gift was filed in.                                           |
| Batch committed        | boolean | Whether the batch was finalised, making the gift visible to the donor. |
| Batch commit requested | boolean | Whether Planning Center accepted a request to commit this batch.       |
| Payment source         | string  | Which system the gift is filed under in Planning Center.               |

#### List Donations

Pull gifts recorded in Planning Center Giving over a date range, for reporting or reconciliation.

**Required permissions:** `giving`.

**Inputs**

| Field                 | Type            | Required | Description                                                                                     |
| --------------------- | --------------- | -------- | ----------------------------------------------------------------------------------------------- |
| Received on or after  | date            | No       | Only include gifts received on or after this date.                                              |
| Received on or before | date            | No       | Only include gifts received on or before this date.                                             |
| Maximum results       | integer         | No       | How many gifts to return. Higher values take longer. Minimum: 1.                                |
| Show advanced filters | boolean         | No       | Reveal filters for fund, payment method, success status and resuming a listing. Default: false. |
| Fund                  | select (string) | No       | Only include gifts designated to this fund. Options load from the selected connection.          |
| Payment method        | select (string) | No       | Only include gifts given this way. Available values: Cash, Check, ACH, Card.                    |
| Successful gifts only | boolean         | No       | Exclude failed and pending gifts. Default: false.                                               |
| Continue from         | string          | No       | Continue a previous listing. Paste the value this action returned as next\_offset.              |

**Outputs**

| Field         | Type          | Description                                                                              |
| ------------- | ------------- | ---------------------------------------------------------------------------------------- |
| Donations     | object\_array | Gifts matching the filters.                                                              |
| Total amount  | number        | Sum of the gifts returned on this page, in dollars.                                      |
| Total matches | integer       | How many gifts match, across all pages.                                                  |
| Next offset   | string        | Pass back as Continue from to fetch the next page. Empty when there are no more results. |

#### List Calendar Events

See what is scheduled on your Planning Center calendar between two dates, including recurring occurrences.

**Required permissions:** `resources`.

**Inputs**

| Field                 | Type            | Required | Description                                                                           |
| --------------------- | --------------- | -------- | ------------------------------------------------------------------------------------- |
| Starting on or after  | datetime        | No       | Only include occurrences that start at or after this moment. Defaults to now.         |
| Starting on or before | datetime        | No       | Only include occurrences that start at or before this moment.                         |
| Maximum results       | integer         | No       | How many occurrences to return. Minimum: 1.                                           |
| Show advanced filters | boolean         | No       | Reveal filters for event name, calendar, and resuming a listing. Default: false.      |
| Event name            | string          | No       | Only include occurrences of events whose name matches.                                |
| Calendar              | select (string) | No       | Only include occurrences on this calendar. Options load from the selected connection. |
| Continue from         | string          | No       | Continue a previous listing. Paste the value this action returned as next\_offset.    |

**Outputs**

| Field         | Type          | Description                                                                              |
| ------------- | ------------- | ---------------------------------------------------------------------------------------- |
| Events        | object\_array | Scheduled occurrences in the time range.                                                 |
| Total matches | integer       | How many occurrences match, across all pages.                                            |
| Next offset   | string        | Pass back as Continue from to fetch the next page. Empty when there are no more results. |

#### List Check-Ins

See who checked in to a service or event, with their check-in time.

**Required permissions:** `check_ins`.

**Inputs**

| Field                   | Type            | Required | Description                                                                                                                                                                                                               |
| ----------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Event                   | select (string) | No       | Only include check-ins for this event, for example Sunday Kids or Youth Group. Options load from the selected connection.                                                                                                 |
| Checked in on or after  | datetime        | No       | Only include check-ins recorded at or after this moment.                                                                                                                                                                  |
| Checked in on or before | datetime        | No       | Only include check-ins recorded at or before this moment.                                                                                                                                                                 |
| Maximum results         | integer         | No       | How many check-ins to return. Minimum: 1.                                                                                                                                                                                 |
| Show advanced filters   | boolean         | No       | Reveal filters for attendee type and resuming a listing. Default: false.                                                                                                                                                  |
| Attendee type           | select (string) | No       | Narrow to one kind of check-in, for example first-time guests or volunteers. Available values: Regular, Guest, Volunteer, Attendee, First-time guest, One-time guest, Not a one-time guest, Checked out, Not checked out. |
| Continue from           | string          | No       | Continue a previous listing. Paste the value this action returned as next\_offset.                                                                                                                                        |

**Outputs**

| Field         | Type          | Description                                                                              |
| ------------- | ------------- | ---------------------------------------------------------------------------------------- |
| Check-ins     | object\_array | Attendance records matching the filters.                                                 |
| Total matches | integer       | How many check-ins match, across all pages.                                              |
| Next offset   | string        | Pass back as Continue from to fetch the next page. Empty when there are no more results. |

### Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

#### Person Created

Starts a workflow whenever a new profile is added to Planning Center People.

Fires whenever someone is added to your Planning Center People directory, whether by an admin, a form submission or another integration. StackAI registers and secures the Planning Center webhook subscription automatically when you enable this trigger.

**Required permissions:** `webhooks`, `people`.

**Event inputs**

| Field      | Type   | Required | Description                            |
| ---------- | ------ | -------- | -------------------------------------- |
| Person ID  | string | Yes      | Planning Center id of the new profile. |
| Full name  | string | Yes      | Name of the person who was added.      |
| First name | string | No       | Given name.                            |
| Last name  | string | No       | Family name.                           |
| Status     | string | No       | Whether the new profile is active.     |
| Created at | string | Yes      | When the profile was created.          |

**Outputs**

| Field      | Type   | Description                            |
| ---------- | ------ | -------------------------------------- |
| Person ID  | string | Planning Center id of the new profile. |
| Full name  | string | Name of the person who was added.      |
| First name | string | Given name.                            |
| Last name  | string | Family name.                           |
| Status     | string | Whether the new profile is active.     |
| Created at | string | When the profile was created.          |

#### Donation Created

Starts a workflow whenever a gift is recorded in Planning Center Giving.

Fires whenever a gift is recorded in Planning Center Giving, whether given online, entered by an admin, or posted through the API. StackAI registers and secures the Planning Center webhook subscription automatically when you enable this trigger. Planning Center only delivers Giving webhook data to a connection held by a user with the Giving Admin or Bookkeeper role; a lesser role produces a subscription that fires with nothing useful.

**Required permissions:** `webhooks`, `giving`.

**Event inputs**

| Field           | Type    | Required | Description                                                 |
| --------------- | ------- | -------- | ----------------------------------------------------------- |
| Donation ID     | string  | Yes      | Planning Center id of the gift.                             |
| Amount          | number  | Yes      | Gift amount in dollars.                                     |
| Amount in cents | integer | Yes      | Gift amount in cents, exactly as Planning Center stores it. |
| Currency        | string  | No       | Currency of the gift.                                       |
| Payment method  | string  | No       | How the gift was given.                                     |
| Received on     | string  | No       | Date the gift was received.                                 |
| Donor           | string  | No       | Profile credited for the gift, if any.                      |
| Created at      | string  | Yes      | When the gift was recorded.                                 |

**Outputs**

| Field           | Type    | Description                                                 |
| --------------- | ------- | ----------------------------------------------------------- |
| Donation ID     | string  | Planning Center id of the gift.                             |
| Amount          | number  | Gift amount in dollars.                                     |
| Amount in cents | integer | Gift amount in cents, exactly as Planning Center stores it. |
| Currency        | string  | Currency of the gift.                                       |
| Payment method  | string  | How the gift was given.                                     |
| Received on     | string  | Date the gift was received.                                 |
| Donor           | string  | Profile credited for the gift, if any.                      |
| Created at      | string  | When the gift was recorded.                                 |

#### Check-In Recorded

Starts a workflow when someone checks in at a kiosk or in the Check-Ins app. Planning Center has no check-in webhook, so this polls for new attendance every five minutes.

Optionally narrow the watch to one event or attendee type. The first poll after enabling this trigger only records the current high-water mark; it never replays existing check-in history.

**Required permissions:** `check_ins`.

**Configuration**

| Field         | Type            | Required | Description                                                                                                                                 |
| ------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Event         | select (string) | No       | Only fire for check-ins to this event. Leave blank to watch every event. Options load from the selected connection.                         |
| Attendee type | select (string) | No       | Only fire for one kind of check-in, for example first-time guests. Available values: Regular, Guest, Volunteer, Attendee, First-time guest. |

**Event inputs**

| Field         | Type   | Required | Description                                                        |
| ------------- | ------ | -------- | ------------------------------------------------------------------ |
| Check-in ID   | string | Yes      | Planning Center id of the attendance record. Default: .            |
| Full name     | string | Yes      | Name on the check-in. Default: .                                   |
| Person ID     | string | No       | Profile this check-in belongs to, when it is linked to one.        |
| Event ID      | string | No       | Event they checked in to.                                          |
| Attendee type | string | No       | Whether they checked in as a regular attendee, guest or volunteer. |
| Checked in at | string | Yes      | When the check-in was recorded. Default: .                         |

**Outputs**

| Field         | Type   | Description                                                        |
| ------------- | ------ | ------------------------------------------------------------------ |
| Check-in ID   | string | Planning Center id of the attendance record.                       |
| Full name     | string | Name on the check-in.                                              |
| Person ID     | string | Profile this check-in belongs to, when it is linked to one.        |
| Event ID      | string | Event they checked in to.                                          |
| Attendee type | string | Whether they checked in as a regular attendee, guest or volunteer. |
| Checked in at | string | When the check-in was recorded.                                    |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/planning-center.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
