EmailReal-timeUpdated June 2026

Customer.io integration

Customer.io email and tracking events into workflows

Customer.io is the messaging platform purpose-built for product-led companies, the lifecycle messaging tool you reach for when triggered emails based on real user behaviour matter more than newsletter campaigns. Four triggers cover the engagement surface: Customer Subscribed (opt-in moment), Email Delivered, Email Opened, Email Link Clicked. Four actions cover the operational side: Identify Person (the upsert primitive in Customer.io's data model), Track Event (custom event for triggering downstream Customer.io campaigns), Send Transactional Email (one-off transactional sends outside the campaign system), Delete Person. The integration uses Customer.io API credentials (Site ID + API Key for the Track API, plus an App API Key for behavioural data). The integration shines when paired with Customer.io's behavioural-trigger campaigns: a workflow Track Event fires a Customer.io campaign that doesn't fire from Customer.io's own SDK, useful when the event source is server-side or comes from another SaaS rather than your app.

Connect Customer.io See 4 triggers

No credit card required · Set up in under 2 minutes

4triggers

4actions

≈ 2 minto set up

Freetier · no card

Triggers

Workflows start when Customer.io does.

4 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.

Real-time · webhook-driven

Trigger live

When customer subscribed

Fires when a customer subscribes to a Customer.io segment or list. The base hook for "they joined → start the welcome journey" or "qualified → add to BDR's outreach queue" cross-app workflows.

See what it returns →

Trigger live

When email delivered

Fires when the recipient mail server accepts the message. Useful for verifying "did the transactional email actually deliver?" workflows.

See what it returns →

Trigger live

When email link clicked

Fires when a recipient clicks a tracked link in a Customer.io email. Payload includes the link URL and recipient. High-signal behavioural hook — branch on URL to route engagement to the right downstream automation.

See what it returns →

Trigger live

When email opened

Fires the first time a recipient opens an email. Useful for engagement-based scoring or for "warm lead — open detected, fire follow-up sequence" cross-app patterns.

See what it returns →

Actions

Do anything Customer.io can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs	Open action
Delete Person	Hard-deletes the person and history. Irreversible — used for GDPR right-to-erasure compliance flows. For soft-removal use suppression list or unsubscribe.	1 input	View
Identify Person	Upserts person-level attributes (plan, country, signup_date, lifetime_value). The state update that drives segmentation and journey targeting. For "external state change → reflect in CIO for accurate audience filtering" sync.	6 inputs	View
Send Transactional Email	Fires a transactional template (designed in Customer.io UI) at a specific recipient with merge data. For "password reset, order confirmation, receipt" workflows where the email content is reviewed in CIO but the trigger is external.	5 inputs	View
Track Custom Event	Pushes a behavioural event into Customer.io's event store. Journeys and campaigns can trigger on these. The standard hook for "server-side action happened → fire CIO event to start the matching journey".	3 inputs	View

Recipes

Pre-built Customer.io workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Customer.io → Slack alerts

AI-triage every Customer.io event, ping the right channel only when it matters.

Customer.io → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Customer.io → Notion database

Turn Customer.io into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Customer.io once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Customer.io field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Customer.io integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Customer.io to Tiny Command?

Open the Tiny Command workflow builder, drop in a Customer.io node, and click Connect. Authorize Customer.io once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Customer.io triggers does Tiny Command support?

Tiny Command supports 4 real-time Customer.io triggers, including "Customer Subscribed", "Email Delivered", "Email Link Clicked". Each trigger fires within seconds of the event happening in Customer.io.

What Customer.io actions can I run from a workflow?

4 Customer.io actions are available out of the box, covering email operations like "Delete Person". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Customer.io integration real-time?

Yes. Customer Subscribed and every other Customer.io trigger uses webhooks or push subscriptions, so workflows fire within seconds of the event in Customer.io rather than on a polling schedule.

Do I need to write code to use Customer.io with Tiny Command?

No. Every Customer.io trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Customer.io API endpoint directly.

How much does the Customer.io integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Customer.io integration itself has no per-app surcharge.

Customer.io integration

Workflows start when Customer.io does.

Do anything Customer.io can do, from a workflow.

Pre-built Customer.io workflows.

Three things worth knowing.

Questions about the Customer.io integration.

More email apps people connect.

Do more with Customer.io.