Skip to Content
ResourcesIntegrationsCustomer SupportCustomer.io

Customer.io

Customer.io icon
Arcade Optimized

Arcade.dev LLM tools for Customer.io

Author:Arcade
Version:0.1.0
Auth:No authentication required
18tools
18require secrets

Customer.io Toolkit

The Customer.io toolkit gives Arcade-powered LLMs direct access to Customer.io workspaces, enabling automation of customer data management, messaging, segmentation, and analytics.

Capabilities

  • Person lifecycle management — create, update, look up, search, and delete person records; record custom events to drive journey triggers.
  • Messaging & delivery — send transactional emails by template, trigger API broadcasts to segments or explicit recipient lists, and retrieve full message/delivery history per person.
  • Campaigns, newsletters & broadcasts — list all campaigns, newsletters, and broadcasts in the workspace; read aggregate delivery metrics for campaigns and newsletters over configurable periods.
  • Segmentation — list workspace segments, inspect segment membership, list segments a person belongs to, and search people by segment and/or attribute.
  • Activity & audit — page through a person's activity timeline with optional filtering by type and name; page through per-person message history.

Secrets

All four secrets are required for full toolkit functionality. Configure them in the Arcade secrets dashboard and reference the Arcade secrets guide.

  • CUSTOMERIO_APP_API_KEY — A Customer.io App API key, used for all Beta/App API calls (person lookup, segmentation, metrics, etc.). Generate one in your Customer.io workspace under Settings → API Credentials → App API Keys. Select the appropriate permission scopes for the operations you need (e.g., customers:read, customers:write, campaigns:read). See the Customer.io App API key docs.

  • CUSTOMERIO_TRACKING_API_KEY — A Customer.io Tracking API key (the secret portion of the site credentials pair), used for write operations against the Track API such as identifying people and recording events. Found in Settings → API Credentials → Tracking API Keys alongside the Site ID. See the Customer.io Tracking API credentials docs.

  • CUSTOMERIO_SITE_ID — The Site ID that pairs with the Tracking API key to authenticate Track API requests. Retrieved from the same Settings → API Credentials → Tracking API Keys page as the Tracking API key.

  • CUSTOMERIO_REGION — The data region for your Customer.io workspace. Accepted values are us (default, track.customer.io) or eu (cdp.customer.io). Find your region in Settings → Workspace Settings. Using the wrong region causes all API calls to fail silently or return 404s. See the Customer.io regional endpoint docs.

Available tools(18)

18 of 18 tools
Operations
Behavior
Tool nameDescriptionSecrets
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
Last updated on