Add Person to Group
Add a person to a Customer.io group to establish a relationship with an object such as a company, account, or project. Supply the person and group IDs and optionally provide group traits.
ActionTry it
Integrate Customer.io
with your AI CRM
Customer.io is a customer engagement platform that enables businesses to send targeted messages to their customers through various channels, including email, SMS, and push notifications.
Explore Triggers and Actions
Author, Version, and Publish Email
Update and version a linked Design Studio email, then publish it. Publishing makes the content live in the linked workflow for every language variant. The email must be linked to a workflow. Multi-language publishes can return pending with a publish_id; check publish status separately until Customer.io reports completion. The update and saved version persist if the publish step fails.
ActionTry it
Create Profile Alias
Create an alias to merge Customer.io profiles for a person with multiple identifiers. The previous ID identifies the source profile and the user ID identifies the destination profile.
ActionTry it
Create Segment
Create an empty manual segment in Customer.io.
ActionTry it
Find Customers by Email
Return Customer.io profiles whose email exactly matches the provided address.
ActionTry it
Get Account Region
Return the region and Track API URL for the connected Customer.io account.
ActionTry it
Get Broadcast Triggers
Retrieve all API trigger instances for a specific broadcast/campaign. Returns trigger metadata including IDs, creation timestamps, and processing status. Use after triggering a broadcast to list all its trigger executions.
ActionTry it
Get Customer Attributes
Return one Customer.io profile's attributes and devices.
ActionTry it
Get Customer.io Workspace Webhooks
Retrieves all reporting webhook configurations from the Customer.io workspace. Reporting webhooks send event notifications (message sent, opened, clicked, etc.) to your specified endpoints. Use this to list all configured webhooks and their settings including subscribed events, endpoints, and status. Returns an empty list if no webhooks are configured.
ActionTry it
Get Integrations
Retrieve a list of integrations in your workspace to discover configured integrations. An HTTP 404 response is returned as an empty list.
ActionTry it
Get Messages
Tool to retrieve a list of messages sent from your workspace. Use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
ActionTry it
Get Newsletter Content Metrics
Retrieve engagement metrics for a Customer.io one-time send variant.
ActionTry it
Get Newsletter Metrics
Retrieve aggregate engagement metrics for a Customer.io one-time send.
ActionTry it
Get Segment Customer Count
Return the current number of profiles in a Customer.io segment.
ActionTry it
Get Segment Details
Tool to retrieve details of a specific segment. Use after identifying the segment ID from list segments.
ActionTry it
Get Segment Membership
Tool to retrieve people in a specific segment. Use when you need to page through segment membership after identifying segment ID.
ActionTry it
Get Segments
Tool to retrieve a list of segments in your workspace. Use when you need to fetch all segments after configuring segment rules.
ActionTry it
Get Transactional Metrics
Return aggregate engagement metrics for a transactional message template.
ActionTry it
Get Trigger
Retrieves details about a specific API-triggered broadcast, including trigger ID, campaign ID, creation timestamp, recipient filter criteria, and personalization data. Use this after triggering a broadcast to verify its configuration and check the data used for message personalization.
ActionTry it
Identify Person
Identify a person in Customer.io and assign traits, creating a profile or updating an existing one. Provide a user ID or anonymous ID to identify the person, and optionally specify when the identification occurred.
ActionTry it
List Activities
Return recent workspace activity-log entries with optional filters.
ActionTry it
List Campaigns
Return Customer.io automations and their metadata.
ActionTry it
List Collections
Tool to list all Collections metadata. Use when you need to retrieve current details of each Collection in your workspace.
ActionTry it
List Customer Attributes
Return attributes and devices for up to 100 Customer.io profiles.
ActionTry it
List IP Addresses
Tool to retrieve the list of IP addresses used by Customer.io for sending messages. Use when you need to allowlist or configure firewall rules for Customer.io's sending infrastructure.
ActionTry it
List Newsletters
Tool to list all newsletters. Use when paginating through newsletter metadata.
ActionTry it
List Snippets
Tool to list all snippets in your workspace. Use when you need to retrieve all reusable content snippets for templating or dynamic content insertion.
ActionTry it
List Transactional Contents
Return every language and content variant of a transactional template.
ActionTry it
List Transactional Messages
Lists all transactional message templates in your Customer.io workspace. Returns the ID and name (trigger name) for each template. Use this when you need to discover available transactional message templates or retrieve their IDs for sending messages via the API.
ActionTry it
List Workspaces
List Customer.io workspaces and their cached usage counts.
ActionTry it
Preview Email
Evaluate a Design Studio email against sample Liquid data without sending.
ActionTry it
Report Push Notification Events
Tool to report push notification events to Customer.io. Use when you need to track device-side push events (opened, converted, delivered). IMPORTANT: This endpoint is deprecated. Use the metrics endpoint instead for reporting push events. This action requires Track API credentials (Basic Auth with siteId:apiKey), not App API credentials.
ActionTry it
Search Customers
Search Customer.io profiles using an audience filter.
ActionTry it
Send Batch CDP Calls
Send multiple CDP calls (identify, track, page, screen, group, alias) in a single batch request. Use this to efficiently send multiple events or profile updates in one API call. The batch endpoint supports up to 500KB total with 32KB per individual call. Each call in the batch can be a different type (identify, track, page, screen, group, or alias). Requirements by call type: - identify/track/page/screen: Require userId or anonymousId - group: Requires groupId (and userId or anonymousId) - track: Requires event name - alias: Requires userId and previousId Note: This action uses the CDP API base URL (https://cdp.customer.io/v1) which differs from the Track API base URL used by some other Customer.io actions.
ActionTry it
Suppress Customer Profile
Suppress a customer profile to permanently delete it and prevent re-adding with the same identifier. IMPORTANT: This action requires Track API credentials (Basic Auth with siteId:apiKey), not App API credentials. Suppression also deletes the customer profile - you don't need to call a separate delete endpoint. Use this for GDPR/CCPA compliance requests. The operation is irreversible and prevents any future attempts to re-add a person with the same identifier (email or ID).
ActionTry it
Track Event
Tool to send an event associated with a person in Customer.io. Records actions users take, along with properties that describe the action. Use when you need to track user behavior, conversions, or custom events for segmentation and campaigns.
ActionTry it
Track Page View
Track page views for website visitors through the Customer.io CDP API, providing a user ID or anonymous ID and optional page properties. The Pipelines API uses basic authorization; this action forwards the connection's authorization headers.
ActionTry it
Track Screen View
Track mobile screen views in Customer.io for analytics and user journey tracking. Records when a user views a screen in your mobile app. Use this when you need to: - Track user navigation patterns in mobile apps - Record screen views for engagement analytics - Trigger workflows based on specific screen visits - Build user journey maps based on screen flow Requirements: - Provide either userId (for known users) or anonymousId (for anonymous users) - Screen name is required to identify which screen was viewed - Optionally include properties for additional context (platform, category, etc.) Note: This endpoint uses the CDP API (cdp.customer.io), not the standard App API.
ActionTry it
Trigger Broadcast
Manually trigger a Customer.io broadcast/campaign to send messages to a defined audience. Use this when you need to: - Send a pre-configured broadcast to specific recipients (by ID or email) - Override the broadcast's default UI-defined audience with custom filtering - Provide personalization data for Liquid template variables - Send individualized content using per_user_data Requirements: - broadcast_id: Must be a valid broadcast ID from Customer.io (find in broadcast's Triggering Details) - Audience: Provide exactly ONE of: recipients, ids, emails, per_user_data, or data_file_url Rate Limits: This endpoint allows one request every 10 seconds per broadcast.
ActionTry it
Unsubscribe from Delivery
Tool to handle custom unsubscribe requests for email deliveries in Customer.io. Use when you need to unsubscribe a person from emails and attribute the action to a specific delivery. IMPORTANT: This action requires Track API credentials (Basic Auth with siteId:apiKey), not App API credentials. The unsubscribe action sets the person's unsubscribed attribute to true.
ActionTry it
How the Customer.io integration works
The Customer.io integration connects your Dench AI CRM directly to Customer.io, so agents can read and act on your Customer.io data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
40 actions are available for agents to invoke on your behalf. Every call runs through Customer.io's own authorization, scoped to the account you connect.
Set up Customer.io in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Customer.io and click Connect — you'll authorize access through Customer.io's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Customer.io in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Customer.io integration work with Dench?
The Dench Customer.io integration connects your AI CRM to Customer.io, so AI agents can work with your Customer.io data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Customer.io via Dench?
The Customer.io integration currently exposes 40 actions, including Add Person to Group, Author, Version, and Publish Email, Create Profile Alias, Create Segment, Find Customers by Email, and Get Account Region. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Customer.io to Dench?
No. You connect Customer.io from your Dench workspace using Customer.io's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Customer.io integration secure?
Connections are authorized through Customer.io's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Customer.io connection from your workspace settings at any time.