Agent skill · marketing growth · jeremylongshore
customerio-primary-workflow
Implement Customer.io primary messaging workflow.
Why this skill is useful
Provides specific implementation patterns and event-driven automation commands for Customer.io that the AI wouldn't reliably generate on its own.
What it needs
Requires customerio-node installed locally. Requires customer.io account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Customer.io Primary Workflow Output A consent-aware workflow with explicit trigger, audience, data contract, message/template version, and owner. A synthetic validation receipt and a scoped rollback/disable action for unexpected delivery behavior. Examples Build the workflow in development using one synthetic profile and a versioned event, confirm trigger conditions and suppression/consent rules, then promote through staging. Enable production through an approved canary audience; pause/disable the workflow if the audience or message behavior does not match the reviewed expectation. Overview Implement Customer.io's core messaging workflow: identify users with segment-ready attributes, track lifecycle events that trigger campaigns, and set up the data layer for automated onboarding, nurture, and re-engagement sequences. Prerequisites customerio-node configured with Track API credentials Campaigns created in Customer.io dashboard (triggered by events you define) Understanding of your user lifecycle stages How Campaigns Work Events tracked via the SDK trigger campaigns you build in the dashboard. The SDK sends the data; the dashboard defines the workflow logic. Instructions Step 1: Define Your Event Taxonomy Step 2: Build the Messaging Service Step 3: Integrate into Application Routes Step 4: Dashboard Campaign Configuration In Customer.io dashboard, create campaigns triggered by these events: Onboarding Campaign: 1. Trigger: Event signedup 2. Wait 5 minutes 3. Send welcome email (use {{ customer.firstname }} and {{ event.method }} Liquid) 4. Wait 1 day 5. Branch: Is emailverified true? No → Send verification reminder Yes → Continue 6. Wait 3 days 7. Send feature tips email 8. Wait 7 days 9. Branch: Has firstprojectcreated event? No → Send activation nudge Yes → End (move to engagement campaign) Cancellation Win-back Campaign: 1. Trigger: Event subscriptioncancelled 2. Wait 3 days 3. Send "We miss you" email with {{ event.reason }} Liquid variable 4. Wait 7 days 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/customerio-primary-workflow