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

The Customer.io toolkit lets LLMs interact with a Customer.io workspace via the Tracking and App APIs. It covers the full lifecycle of contacts, messaging, and analytics — from identifying people and recording events through sending transactional emails and triggering broadcasts.

Capabilities

  • Contact management: Create, update, look up, search, and delete person profiles; resolve by email or ID; handle multi-match edge cases.
  • Activity & message history: Retrieve a person's timeline of activities (filterable by type/name) and full message/delivery history.
  • Segments: List workspace segments, check which segments a person belongs to, and enumerate segment members.
  • Campaigns, newsletters & 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 transactional emails to a single recipient by template ID.
  • Event tracking: Record named custom events on a person's timeline to drive lifecycle journeys.

Secrets

This toolkit uses no OAuth flow. All credentials are supplied as secrets.

  • CUSTOMERIO_SITE_ID — The Site ID for your Customer.io workspace, used to authenticate Tracking API calls. Find it in the Customer.io dashboard under Settings → API Credentials → Tracking API. Customer.io API Credentials docs

  • CUSTOMERIO_TRACKING_API_KEY — The Tracking API Key paired with the Site ID above. Retrieved from the same Settings → API Credentials → Tracking API page. This key authenticates event, identify, and delete calls sent to the Tracking API endpoint.

  • CUSTOMERIO_APP_API_KEY — A Bearer token for the Customer.io App API (used for reading campaigns, newsletters, segments, sending transactional email, triggering broadcasts, etc.). Generate one in Settings → API Credentials → App API Keys. Scope the key to the minimum permissions your use case requires. Customer.io App API auth docs

  • CUSTOMERIO_REGION — Specifies the data region for your workspace (US or EU). This determines which API base URLs are used. You can confirm your region in Settings → Workspace Settings. Provide the appropriate string so requests are routed to the correct regional endpoint.

See the Arcade secrets guide for how to configure secrets, and manage them 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