Customer.io Automation
Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio
- License 许可
- MIT
- 最近更新
- 2026-11-03
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- Customer.io Automation
- requires
- { "mcp": [ "rube" ] }
- description
- Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio
03 SKILL.md 正文
Customer.io Automation
Automate customer engagement operations -- trigger targeted broadcasts, retrieve delivery metrics, manage audience segments, list newsletters and transactional templates, and inspect trigger execution history -- all orchestrated through the Composio MCP integration.
Toolkit docs: composio.dev/toolkits/customerio
Setup
- Connect your Customer.io account through the Composio MCP server at
https://rube.app/mcp - The agent will prompt you with an authentication link if no active connection exists
- Once connected, all
CUSTOMERIO_*tools become available for execution
Core Workflows
1. Trigger a Broadcast
Manually fire a pre-configured broadcast to a specific audience with personalization data.
Tool: CUSTOMERIO_TRIGGER_BROADCAST
| Parameter | Type | Required | Description |
|---|---|---|---|
broadcast_id |
integer | Yes | Broadcast ID from Customer.io Triggering Details |
ids |
array | No | List of customer IDs to target |
emails |
array | No | List of email addresses to target |
recipients |
object | No | Complex filter with and/or/not/segment operators |
per_user_data |
array | No | Per-user personalization with id/email + data |
data |
object | No | Global key-value data for Liquid template personalization |
data_file_url |
string | No | URL to JSON file with per-line user data |
email_add_duplicates |
boolean | No | Allow duplicate recipients (default: false) |
email_ignore_missing |
boolean | No | Skip people without emails (default: false) |
id_ignore_missing |
boolean | No | Skip people without customer IDs (default: false) |
Important: Provide exactly ONE audience option: recipients, ids, emails, per_user_data, or data_file_url. Rate limit: 1 request per 10 seconds per broadcast.
2. Retrieve Message Delivery Metrics
Fetch paginated delivery metrics for messages with filtering by campaign, type, and time window.
Tool: CUSTOMERIO_GET_MESSAGES
| Parameter | Type | Required | Description |
|---|---|---|---|
type |
string | No | Message type: email, webhook, twilio, slack, push, in_app |
metric |
string | No | Metric: attempted, sent, delivered, opened, clicked, converted |
campaign_id |
integer | No | Filter by campaign ID |
newsletter_id |
integer | No | Filter by newsletter ID |
action_id |
integer | No | Filter by action ID |
start_ts |
integer | No | Start of time window (Unix timestamp) |
end_ts |
integer | No | End of time window (Unix timestamp) |
limit |
integer | No | Results per page, 1-1000 (default: 50) |
start |
string | No | Pagination token from previous response next value |
drafts |
boolean | No | Return draft messages instead of active/sent |
3. List Audience Segments
Retrieve all segments defined in your workspace for audience analysis and broadcast targeting.
Tool: CUSTOMERIO_GET_SEGMENTS
No parameters required -- returns all segments with IDs and metadata.
Use segment IDs when targeting broadcasts via the recipients.segment.id filter.
4. List Newsletters
Paginate through all newsletter metadata for tracking and analysis.
Tool: CUSTOMERIO_LIST_NEWSLETTERS
| Parameter | Type | Required | Description |
|---|---|---|---|
limit |
integer | No | Max per page, 1-100 |
sort |
string | No | asc (chronological) or desc (reverse) |
start |
string | No | Pagination cursor from previous response next value |
5. Discover Transactional Message Templates
List all transactional message templates to find IDs for sending via the API.
Tool: CUSTOMERIO_LIST_TRANSACTIONAL_MESSAGES
No parameters required -- returns template IDs and trigger names.
6. Inspect Broadcast Trigger History
Review all trigger executions for a broadcast and inspect individual trigger details.
Tools: CUSTOMERIO_GET_TRIGGERS and CUSTOMERIO_GET_TRIGGER
List all triggers for a broadcast:
| Parameter | Type | Required | Description |
|---|---|---|---|
broadcast_id |
integer | Yes | The broadcast/campaign ID |
Get a specific trigger:
| Parameter | Type | Required | Description |
|---|---|---|---|
broadcast_id |
integer | Yes | The campaign/broadcast ID |
trigger_id |
string | Yes | Trigger identifier (e.g., 456 or 5-37) |
Known Pitfalls
| Pitfall | Details |
|---|---|
| Mutually exclusive audience params | CUSTOMERIO_TRIGGER_BROADCAST requires exactly ONE of recipients, ids, emails, per_user_data, or data_file_url -- providing multiple causes errors |
| Rate limiting on broadcasts | Broadcasts are limited to 1 trigger request per 10 seconds per broadcast ID |
| Unix timestamp format | start_ts and end_ts in CUSTOMERIO_GET_MESSAGES must be Unix timestamps, not ISO strings |
| Pagination tokens | Messages and newsletters use cursor-based pagination via the start parameter -- use the next value from previous responses |
| Segment ID resolution | To target a segment in a broadcast, first fetch segment IDs via CUSTOMERIO_GET_SEGMENTS, then reference by ID in recipients.segment.id |
Quick Reference
| Tool Slug | Purpose |
|---|---|
CUSTOMERIO_TRIGGER_BROADCAST |
Trigger a broadcast to a defined audience |
CUSTOMERIO_GET_MESSAGES |
Retrieve message delivery metrics with filters |
CUSTOMERIO_GET_SEGMENTS |
List all audience segments |
CUSTOMERIO_GET_SEGMENT_DETAILS |
Get details for a specific segment |
CUSTOMERIO_LIST_NEWSLETTERS |
Paginate through newsletters |
CUSTOMERIO_LIST_TRANSACTIONAL_MESSAGES |
List transactional message templates |
CUSTOMERIO_GET_TRIGGERS |
List all trigger executions for a broadcast |
CUSTOMERIO_GET_TRIGGER |
Inspect a specific trigger execution |
Powered by Composio
04 同仓库更多 Skills
x-article-draft-uploader
把本地 Markdown 转为经核验的 X Articles 新草稿。适用于需要保留首图封面、正文图片相对位置,并在独立 Playwright 会话中复用用户已授权 Chrome 登录态的任务;不负责公开发布。
wecom-operations
通过用户已配置的官方 wecom-cli 管理企业微信文档、智能文档、待办、会议和日程。适合创建或查询这些云端对象、把本地 Markdown 转为智能文档,以及在明确确认后更新或取消对象;不发送消息、不控制桌面客户端。
wecom-local-vault
Inspect authorized local WeCom databases on macOS, create private plaintext snapshots, and query or export contacts, conversations, and messages without modifying the source account store. Use when the user asks to parse 企业微信/WeCom local data, recover a private database snapshot, inspect local contacts or sessions, search chat history, or export a bounded conversation.
wechat-reading
Read and analyze WeRead/微信读书 search results, book metadata, bookshelf entries, progress, notes, highlights, public reviews, recommendations, and reading statistics through the official read-only Agent Gateway. Use for WeRead account questions or exports; do not imply that the current Gateway can add, remove, upload, rate, like, or edit content.
wechat-mp-batch-exporter
Build a bounded, private archive from known WeChat Official Account article URLs or an owner-authorized account-history export, with explicit reconciliation of article, publish-group, and platform-marked-original counts. Use for batch body capture, history normalization, or enhanced metrics/comments workflows. Do not use for a one-page summary or to automate the WeChat client.
wechat-local-vault
在 macOS 本机建立并查询私有微信数据快照。适用于盘点数据库、离线校验已有密钥候选、创建全量或增量明文快照、查会话与联系人、按时间检索消息、导出指定聊天、查看朋友圈或收藏,以及准备群聊摘要素材。所有查询只读,默认隐藏内部账号标识,不操控微信界面,也不发送任何内容。