EmailReal-timeUpdated May 2026

Iterable

Iterable user events and triggered email

Iterable is the cross-channel marketing platform (email + push + SMS + in-app) used by B2C teams that have outgrown the SMB ESPs. Tiny Command exposes five actions, no triggers (Iterable's "event" architecture means most state changes are events you push into Iterable rather than events Iterable pushes out — outbound webhooks exist but are configured per-workflow inside Iterable Studio rather than via API): Update User (upsert by email or userId; passes data fields used by Iterable's segments and templates), Subscribe to List, Add UserList (the same concept but using the List API endpoint for bulk membership), Send Triggered Email (fire a specific transactional template to a user, with data merged into the template), Track Event (push a custom event into Iterable's event log — the granular signal that powers cart-abandonment, browse-abandonment, post-purchase workflows). The connection uses an Iterable API key from the Integrations settings; keys are scoped (Server-side, JS, Mobile) — use a Server-side key for backend automation.

Connect Iterable

0triggers

6actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Iterable 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
Iterable Add to UserList (Bulk)	Bulk-subscribe via the lists/subscribe endpoint — accepts an array of subscribers in one call. Much faster for bulk migrations or daily syncs than per-user Subscribe to List.	1 fields	View →
Get Iterable User	Returns the user record by email or userId with all data fields. The standard lookup for enrichment workflows or for "is this user in Iterable already" pre-flight checks.	1 fields	View →
Iterable Send Triggered Email	Fires a specific transactional template at a user with merged data. Respects user subscription preferences. For "password reset, order confirmation" workflows where the email content is reviewed in Iterable but the trigger is external.	3 fields	View →
Subscribe to List (Single User)	Single-user list subscription. For bulk operations (10+ users), use Add UserList which is much more efficient per-user.	2 fields	View →
Track Iterable Event	Pushes a custom behavioural event with optional properties. Drives Iterable workflow triggers. For "server-side action happened → start the matching journey" patterns.	4 fields	View →
Update Iterable User	Upserts user data fields (plan, country, signup_date, lifetime_value). The state-update hook for keeping audience segmentation accurate.	4 fields	View →

Recipes

Pre-built Iterable workflows.

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

Iterable → Slack alerts

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

Iterable → Google Sheets log

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

Iterable → Notion database

Turn Iterable 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 Iterable 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 Iterable 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 Iterable integration.

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

How do I connect Iterable to Tiny Command?

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

What Iterable triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Iterable today. Use Tiny Command's universal Webhook or Schedule trigger to start Iterable workflows, then run any Iterable action you need.

What Iterable actions can I run from a workflow?

6 Iterable actions are available out of the box, covering email operations like "Iterable Add to UserList (Bulk)". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Iterable integration real-time?

Iterable actions execute synchronously inside your workflow. Tiny Command waits for Iterable's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Iterable with Tiny Command?

No. Every Iterable 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 Iterable API endpoint directly.

How much does the Iterable 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 Iterable integration itself has no per-app surcharge.