| name | customerio-core-feature |
| description | Implement Customer.io core features: transactional messages,
API-triggered broadcasts, segments, and person merge.
Trigger: "customer.io segments", "customer.io transactional",
"customer.io broadcast", "customer.io merge users", "customer.io send email".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(npx:*), Glob, Grep |
| version | 1.14.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","customer-io","transactional","broadcasts","segments"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Customer.io Core Features
Overview
Implement Customer.io's key platform features: transactional emails/push (password resets, receipts), API-triggered broadcasts (one-to-many on demand), segment-driving attributes, anonymous-to-known user merging, and person suppression/deletion.
Prerequisites
customerio-node installed
- Track API credentials (
CUSTOMERIO_SITE_ID + CUSTOMERIO_TRACK_API_KEY)
- App API credential (
CUSTOMERIO_APP_API_KEY) — required for transactional + broadcasts
Instructions
Feature 1: Transactional Email
Transactional messages are opt-in-implied messages (receipts, password resets). Create the template in Customer.io dashboard first, then call the API with data.
import { APIClient, SendEmailRequest, RegionUS } from "customerio-node";
const api = new APIClient(process.env.CUSTOMERIO_APP_API_KEY!, {
region: RegionUS,
});
async function sendPasswordReset(email: string, userId: string, resetUrl: string) {
const request = new SendEmailRequest({
to: email,
transactional_message_id: "3",
: {
: resetUrl,
: ,
: ,
},
: { : userId },
});
response = api.(request);
response;
}
() {
request = ({
: email,
: ,
: {
: order.,
: order.,
: order.,
: ().(),
},
: { : userId },
});
api.(request);
}