Skip to main content
Agent skill

Customer.Io Automation

Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Customer.Io Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio

When not to use it

Skip Customer.Io Automation when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/customerio-automation
# Save SKILL.md to ~/.claude/skills/customerio-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/customerio-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/customerio-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Customer.Io Automation skill for this task: Use Customer.Io Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# 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](https://composio.dev/toolkits/customerio)

---

## Setup

1. Connect your Customer.io account through the Composio MCP server at `https://rube.app/mcp` 2. The agent will prompt you with an authentication link if no active connection exists 3. 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](https://composio.dev)*

Intended uses

  • Use Customer.Io Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.