> 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/customer.io.md).

# Customer.io

Create and update people and ingest customer data in Customer.io, the messaging and marketing automation platform.

### Connectors

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

| Connector   | Authentication   |
| ----------- | ---------------- |
| Customer.io | API key or token |

#### Customer.io

Connect to Customer.io to create and update people and ingest customer data via the Track API.

**Set up in Customer.io**

1. Prepare the Customer.io account or service that the workflow will access. Grant access to the required resources and operations.
2. **Track API Site ID:** Your Customer.io Track API Site ID. Find it in Customer.io under Account Settings > API Credentials > Tracking API Keys.
3. **Track API Key:** Your Customer.io Track API Key, paired with the Site ID for HTTP Basic auth. Find it in Account Settings > API Credentials > Tracking API Keys.
4. **App API Key:** Your Customer.io App API Key (Bearer token). Required — it powers the connection health check and read actions. Create one in Account Settings > API Credentials > App API Keys.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Customer.io**.
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                                                                                                                                                                                                                                               |
| ----------------- | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Track API Site ID | Yes                      | Your Customer.io Track API Site ID. Find it in Customer.io under Account Settings > API Credentials > Tracking API Keys. [Provider instructions](https://fly.customer.io/settings/api_credentials).                                                         |
| Track API Key     | Yes                      | Your Customer.io Track API Key, paired with the Site ID for HTTP Basic auth. Find it in Account Settings > API Credentials > Tracking API Keys. [Provider instructions](https://fly.customer.io/settings/api_credentials).                                  |
| App API Key       | Yes                      | Your Customer.io App API Key (Bearer token). Required — it powers the connection health check and read actions. Create one in Account Settings > API Credentials > App API Keys. [Provider instructions](https://fly.customer.io/settings/api_credentials). |
| Region            | Optional / as applicable | The region your Customer.io workspace lives in. US uses track.customer.io / api.customer.io; EU uses track-eu.customer.io / api-eu.customer.io. Credentials are only valid on their own region.                                                             |

#### 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 **Customer.io** 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 or Update Person

Create or update a person in Customer.io.

**Inputs**

| Field               | Type     | Required | Description                                                      |
| ------------------- | -------- | -------- | ---------------------------------------------------------------- |
| Customer Identifier | string   | Yes      | The person's unique identifier (email, customer ID, or cio\_id). |
| Email               | string   | No       | Email address to store on the person (optional).                 |
| Attributes (JSON)   | textarea | No       | Custom attributes as a JSON object (optional).                   |

**Outputs**

| Field           | Type   | Description                                               |
| --------------- | ------ | --------------------------------------------------------- |
| Identifier      | string | The identifier of the person that was created or updated. |
| Attributes Sent | object | The attribute payload that was sent to Customer.io.       |
| Result Message  | string | Human-readable result summary.                            |

#### Track Event

Record a behavioral event for a person in Customer.io.

**Inputs**

| Field               | Type     | Required | Description                                                         |
| ------------------- | -------- | -------- | ------------------------------------------------------------------- |
| Customer Identifier | string   | Yes      | The person to track the event for (email, customer ID, or cio\_id). |
| Event Name          | string   | Yes      | The name of the event, e.g. 'purchase' or 'feature\_accessed'.      |
| Event Data (JSON)   | textarea | No       | Custom properties for the event, as a JSON object (optional).       |

**Outputs**

| Field           | Type   | Description                                              |
| --------------- | ------ | -------------------------------------------------------- |
| Identifier      | string | The identifier of the person the event was tracked for.  |
| Event Name      | string | The name of the event that was tracked.                  |
| Event Data Sent | object | The event property payload that was sent to Customer.io. |
| Result Message  | string | Human-readable result summary.                           |

#### Delete Person

Permanently delete a person from Customer.io.

**Inputs**

| Field               | Type   | Required | Description                                                        |
| ------------------- | ------ | -------- | ------------------------------------------------------------------ |
| Customer Identifier | string | Yes      | The person to permanently delete (email, customer ID, or cio\_id). |

**Outputs**

| Field          | Type   | Description                                    |
| -------------- | ------ | ---------------------------------------------- |
| Identifier     | string | The identifier of the person that was deleted. |
| Result Message | string | Human-readable result summary.                 |

#### List Segments

List segments in a Customer.io workspace.

**Inputs**

| Field  | Type    | Required | Description                                                    |
| ------ | ------- | -------- | -------------------------------------------------------------- |
| Limit  | integer | No       | Maximum number of segments to return.                          |
| Cursor | string  | No       | Pagination cursor from a previous call's 'Next Cursor' output. |

**Outputs**

| Field          | Type    | Description                                       |
| -------------- | ------- | ------------------------------------------------- |
| Segments       | array   | The segments returned by Customer.io.             |
| Count          | integer | Number of segments returned in this page.         |
| Next Cursor    | string  | Cursor for the next page, if more segments exist. |
| Result Message | string  | Human-readable result summary.                    |

#### Search Customers

Find customers in Customer.io by email or customer ID.

**Inputs**

| Field       | Type   | Required | Description                                            |
| ----------- | ------ | -------- | ------------------------------------------------------ |
| Email       | string | No       | Find a customer by exact email match.                  |
| Customer ID | string | No       | Find a customer by exact customer ID or cio\_id match. |

**Outputs**

| Field          | Type    | Description                           |
| -------------- | ------- | ------------------------------------- |
| Customers      | array   | Customers matching the given filters. |
| Count          | integer | Number of matching customers found.   |
| Result Message | string  | Human-readable result summary.        |

### 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/customer.io.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.
