Customer.io
Arcade.dev LLM tools for Customer.io
0.1.0Customer.io is a customer messaging and lifecycle-automation platform. This Arcade toolkit exposes Customer.io's App API and Tracking API as LLM-callable tools, enabling agents to manage people, query analytics, and send or trigger messages.
Capabilities
- People management: Look up, create/update, and delete person profiles; search by segment membership or attribute; list activities, messages, and segment memberships for a person.
- Segments: List all workspace segments, inspect segment members, and filter or build audiences by combining segment and attribute criteria.
- Campaigns, newsletters, and broadcasts: List campaigns, newsletters, and broadcasts; read aggregate delivery metrics for campaigns and newsletters; trigger API broadcasts to segments or explicit recipient lists.
- Transactional messaging: List transactional message templates and send a transactional email to a single recipient by template ID.
- Event tracking: Record named custom events on a person's timeline to drive lifecycle journeys and automation.
Secrets
All four secrets below are required to use this toolkit. Set them in the Arcade secrets dashboard and refer to the Arcade secrets guide for configuration details.
-
CUSTOMERIO_APP_API_KEY— A Customer.io App API key, used to authenticate calls to the App API (people lookup, metrics, segments, campaigns, etc.). Generate one in your Customer.io workspace under Settings → API & Webhooks → App API Keys. The key requires no additional scope selection; it inherits your account's permissions. Customer.io App API key docs. -
CUSTOMERIO_TRACKING_API_KEY— A Customer.io Tracking API key (also called the API Secret in some UI versions), used to authenticate calls to the Tracking API (identify people, record events). Found in your workspace under Settings → API & Webhooks → Tracking API Keys alongside the Site ID. Customer.io Tracking API docs. -
CUSTOMERIO_SITE_ID— The Site ID paired withCUSTOMERIO_TRACKING_API_KEYfor Tracking API Basic Auth. Retrieved from the same Settings → API & Webhooks → Tracking API Keys page in your Customer.io workspace. -
CUSTOMERIO_REGION— Identifies which Customer.io data center your workspace is hosted in. Accepted values are typicallyus(default,track.customer.io) oreu(cdp.customer.io). Check your workspace region in Settings → Workspace Settings. Customer.io regions docs.
Available tools(18)
| Tool name | Description | Secrets | |
|---|---|---|---|
Delete a person record to honor a data-removal request.
Deleting a person who does not exist is accepted as a no-op. | 2 | ||
Read a campaign's aggregate delivery metrics over a period. | 2 | ||
Read a newsletter's aggregate delivery metrics over a period. | 2 | ||
Look up a person's profile by email or id.
Resolves the person by whichever identifier is supplied; an email shared by
several people reports every match in the result. | 2 | ||
Create or update a person and their attributes.
Existing attributes not named in this call are preserved; named attributes
are added or overwritten. | 2 | ||
List the workspace's broadcasts to discover ids that can be triggered. | 2 | ||
List the campaigns in the workspace. | 2 | ||
List the newsletters in the workspace. | 2 | ||
List a person's recent activities, most recent first, resolved by email
or id. Optionally filter by activity type and/or name; filtering by name
requires an activity type. When an email matches several people, the first
match's activities are returned. | 2 | ||
List a person's message and delivery history, most recent first,
resolved by email or id. When an email matches several people, the first
match's messages are returned. | 2 | ||
List the segments a person belongs to, resolved by email or id. When an
email matches several people, the first match's segments are returned. | 2 | ||
List the ids of the people in a segment and the segment's total size. | 2 | ||
List the segments defined in the workspace. | 2 | ||
List the transactional message templates in the workspace. | 2 | ||
Record a named custom event on a person's timeline to drive lifecycle
journeys. | 2 | ||
Find people by segment membership and/or an attribute, to build an
audience without a known id. Supply at least one of a segment or an
attribute name; both combine with AND. | 2 | ||
Send a transactional email to one recipient by its template id. | 2 | ||
Trigger an API broadcast to a segment or an explicit recipient list. | 2 |