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 platform for sending targeted emails, push notifications, and in-app messages. This Arcade toolkit exposes Customer.io's App API and Tracking API as LLM-callable tools, covering profile management, event tracking, messaging, and analytics.

Capabilities

  • Person management: Create, update, look up, search, and delete person profiles; resolve by email or ID; handle duplicate-email scenarios gracefully.
  • Event & activity tracking: Record named custom events on a person's timeline; browse a person's activity history with optional type/name filters.
  • Message history & transactional sending: Retrieve a person's delivery history, list transactional templates, and send transactional emails by template ID.
  • 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.
  • Audience & segment operations: List all workspace segments, inspect segment membership, list a person's segments, and search people by segment and/or attribute.

Secrets

This toolkit requires no OAuth flow; all authentication is handled via secrets passed at call time.

  • CUSTOMERIO_APP_API_KEY — A Customer.io App API key, used for all App API calls (profile reads/writes, metrics, segments, messaging). Generate one in your Customer.io workspace under Settings → API Credentials → App API Keys. The key requires access to the scopes matching the tools you use (e.g., Journeys Data, Reporting). See the Customer.io App API key docs for details.

  • CUSTOMERIO_TRACKING_API_KEY — A Customer.io Tracking API key (also called the API Secret in the UI), used for calls that write events or identify people via the Tracking API. Find it in Settings → API Credentials → Tracking API Keys. Each key is scoped to a single workspace/site. See the Customer.io Tracking API docs.

  • CUSTOMERIO_SITE_ID — The Site ID that pairs with the Tracking API key to authenticate Tracking API requests. Found alongside the Tracking API key in Settings → API Credentials → Tracking API Keys.

  • CUSTOMERIO_REGION — Identifies which Customer.io data center hosts your workspace (us or eu). Determines the base URL used for all API calls. Find your region in Settings → Workspace Settings. If omitted or wrong, API calls will fail or return no data.

Configure secrets in the Arcade dashboard or via the API: Arcade secrets guide. You can also manage secrets 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