Customer.io
Arcade.dev LLM tools for Customer.io
0.1.0Customer.io is a customer messaging platform for lifecycle email, push, and in-app campaigns. This Arcade toolkit gives LLMs programmatic access to Customer.io workspaces — managing people, events, segments, campaigns, newsletters, broadcasts, and transactional messages.
Capabilities
- People management — create, update, look up, and delete person profiles; record custom events to drive lifecycle journeys.
- Audience & segmentation — list workspace segments, inspect segment membership, list or search people by segment and attribute filters.
- Campaign & newsletter analytics — retrieve aggregate delivery metrics for campaigns and newsletters; list all campaigns, newsletters, and broadcasts in the workspace.
- Messaging operations — send transactional emails by template ID, trigger API broadcasts to segments or explicit recipient lists, and list transactional message templates.
- Person history — retrieve a person's activity timeline, message/delivery history, and segment memberships by email or ID.
Secrets
This toolkit requires no OAuth flow — all authentication is handled via secrets passed at runtime.
CUSTOMERIO_APP_API_KEY
A Customer.io App API key, used to call the Customer.io App API (reporting, people lookup, segments, campaigns, newsletters, broadcasts). Generate one in your Customer.io workspace under Settings → API Credentials → App API Keys. Keys are workspace-scoped; grant only the permissions your integration needs.
CUSTOMERIO_TRACKING_API_KEY
The Tracking API key (also called the API key in older docs), paired with the Site ID, used to authenticate calls to the Customer.io Track API (identify people, record events). Found in Settings → API Credentials → Tracking API Keys.
CUSTOMERIO_SITE_ID
The Site ID that identifies your workspace for Tracking API calls. Located alongside the Tracking API key in Settings → API Credentials → Tracking API Keys.
CUSTOMERIO_REGION
Indicates which Customer.io data region your workspace is hosted in (us or eu). This determines which API base URLs are used (e.g., api.customer.io vs eu-api.customer.io). Find your region in Settings → Workspace Settings or infer it from the URL you use to log in to Customer.io.
See the Arcade secrets docs for how to store and reference these values: https://docs.arcade.dev/en/guides/create-tools/tool-basics/create-tool-secrets. You can also manage secrets directly at https://api.arcade.dev/dashboard/auth/secrets.
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 |