# Customer.io AI integration on Definable

> Customer.io is a customer engagement platform that enables businesses to send targeted messages to their customers through various channels, including email, SMS, and push notifications.

## What this connects

Customer.io is a customer engagement platform that enables businesses to send targeted messages to their customers through various channels, including email, SMS, and push notifications.

Vendor: https://customer.io/

## Tools available

**23** tools available. First 12:

- `CUSTOMERIO_ADD_PERSON_TO_GROUP` — Add Person to Group — Tool to add people to a group in Customer.io. Groups represent objects like companies, accounts, or projects that people belong to. Use when you need to establish relationships between people and organizational entities.
- `CUSTOMERIO_CREATE_ALIAS` — Create Profile Alias — Tool to create an alias to merge multiple profiles in Customer.io. Use when you need to support multiple identifiers for a single person. The alias operation moves all data from the previous_id profile to the user_id profile, consolidating them into a single canonical profile.
- `CUSTOMERIO_CUSTOMER_IO_SUPPRESS_PERSON` — Suppress Customer Profile — Suppress a customer profile to permanently delete it and prevent re-adding with the same identifier. IMPORTANT: This action requires Track API credentials (Basic Auth with siteId:apiKey), not App API credentials. Suppression also deletes the customer profile - you don't need to call a separate delete endpoint. Use this for GDPR/CCPA compliance requests. The operation is irreversible and prevents any future attempts to re-add a person with the same identifier (email or ID).
- `CUSTOMERIO_GET_INTEGRATIONS` — Get Integrations — Tool to retrieve a list of integrations in your workspace. Use when you need to discover configured integrations.
- `CUSTOMERIO_GET_MESSAGES` — Get Messages — Tool to retrieve a list of messages sent from your workspace. Use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
- `CUSTOMERIO_GET_SEGMENT_DETAILS` — Get Segment Details — Tool to retrieve details of a specific segment. Use after identifying the segment ID from list segments.
- `CUSTOMERIO_GET_SEGMENT_MEMBERSHIP` — Get Segment Membership — Tool to retrieve people in a specific segment. Use when you need to page through segment membership after identifying segment ID.
- `CUSTOMERIO_GET_SEGMENTS` — Get Segments — Tool to retrieve a list of segments in your workspace. Use when you need to fetch all segments after configuring segment rules.
- `CUSTOMERIO_GET_TRIGGER` — Get Trigger — Retrieves details about a specific API-triggered broadcast, including trigger ID, campaign ID, creation timestamp, recipient filter criteria, and personalization data. Use this after triggering a broadcast to verify its configuration and check the data used for message personalization.
- `CUSTOMERIO_GET_TRIGGERS` — Get Broadcast Triggers — Retrieve all API trigger instances for a specific broadcast/campaign. Returns trigger metadata including IDs, creation timestamps, and processing status. Use after triggering a broadcast to list all its trigger executions.
- `CUSTOMERIO_GET_WEBHOOKS` — Get Customer.io Workspace Webhooks — Retrieves all reporting webhook configurations from the Customer.io workspace. Reporting webhooks send event notifications (message sent, opened, clicked, etc.) to your specified endpoints. Use this to list all configured webhooks and their settings including subscribed events, endpoints, and status. Returns an empty list if no webhooks are configured.
- `CUSTOMERIO_IDENTIFY_PERSON` — Identify Person — Tool to identify a person and assign traits to them in Customer.io. Creates a new person profile if it doesn't exist, or updates an existing one. Use when adding new users, updating user profiles, or tracking anonymous visitors. Either user_id or anonymous_id must be provided.

## Auth

Auth schemes: `API_KEY`.

## How agents use Customer.io

Inside a Definable workflow, Customer.io is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Customer.io** — the Researcher (GPT-5.5) pulls context from Customer.io (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Customer.io** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Customer.io (create record, post message, draft email).
- **Designer / Engineer → Distributor → Customer.io** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Customer.io (attach file, open PR comment, post status).

The Verifier checks every Customer.io call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- marketing automation — https://definable.ai/apps/category/marketing-automation/
- drip emails — https://definable.ai/apps/category/drip-emails/

## Related

- HTML page: https://definable.ai/apps/customerio/
- Same category (marketing automation): https://definable.ai/apps/category/marketing-automation/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt