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 is a customer engagement and messaging platform; this Arcade toolkit lets LLM agents read and write Customer.io workspace data — people, segments, campaigns, and messages — without manual API calls.

Capabilities

  • People management — create, update, look up, search, and delete person records; resolve by email or id; support multi-match edge cases.
  • Activity & message history — list a person's recent events/activities (filterable by type and name) and full message/delivery history.
  • Segments — list all workspace segments, list members of a segment, and retrieve the segments a specific person belongs to.
  • Campaigns, newsletters & broadcasts — list campaigns and newsletters, read their aggregate delivery metrics, list available broadcasts, and trigger API broadcasts to segments or explicit recipient lists.
  • Transactional messaging — list transactional email templates and send a transactional email to a single recipient by template id.
  • Custom events — record named events on a person's timeline to drive lifecycle journeys and automation triggers.

Secrets

All four secrets must be configured in the Arcade secret store before using this toolkit.

  • 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. Choose the appropriate permission scope for your use case (read-only vs. full access).

  • CUSTOMERIO_TRACKING_API_KEY — A Customer.io Tracking API key, used to identify people and record events via the Tracking API. Retrieve it from Settings → API Credentials → Tracking API Keys in your workspace dashboard.

  • CUSTOMERIO_SITE_ID — The workspace Site ID, paired with the Tracking API key to authenticate Tracking API requests. Found alongside the Tracking API key at Settings → API Credentials → Tracking API Keys.

  • CUSTOMERIO_REGION — The data region your Customer.io workspace is hosted in (us or eu). This determines which API base URLs are used. Check your workspace URL or region setting in Settings → Workspace Settings to confirm which region applies.

See Arcade secrets configuration for how to register secrets, or manage them directly at https://api.arcade.dev/dashboard/auth/secrets.

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