ActionIterableUpdated May 2026
How do I subscribe a single user to an Iterable list?
Short answer: Drop the "Iterable → Subscribe to List (Single User)" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
List ID listId | string | Required | — |
Subscribers (array of {email, userId, dataFields}) subscribers | array | Required | Example: [{"email":"jane@x.com"}] |
Sample request
{"listId": "{{trigger.listId}}","subscribers": "{{trigger.subscribers}}"}
Returns
{"failCount": 0,"successCount": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Subscribe to List (Single User).
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Subscribe to List (Single User).
What does the Subscribe to List (Single User) action do in Iterable?
Single-user list subscription. For bulk operations (10+ users), use Add UserList which is much more efficient per-user.
What inputs does Subscribe to List (Single User) require?
Required: List ID, Subscribers (array of {email, userId, dataFields}). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Iterable returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Subscribe to List (Single User) support batch operations?
Yes. Run Subscribe to List (Single User) inside a Loop node to process arrays. Tiny Command handles Iterable's rate limits automatically so you don't have to throttle manually.
More actions
Other Iterable actions.
Action
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.
ActionGet 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.
ActionIterable 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.
ActionTrack Iterable Event
Pushes a custom behavioural event with optional properties. Drives Iterable workflow triggers. For "server-side action happened → start the matching journey" patterns.
ActionUpdate Iterable User
Upserts user data fields (plan, country, signup_date, lifetime_value). The state-update hook for keeping audience segmentation accurate.
Send subscribe to list (single user) from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
