ActionIterableUpdated September 2026
How do I bulk-add users to an Iterable list?
Short answer: You can iterable add to userlist (bulk) in Iterable by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Iterable Iterable Add to UserList (Bulk) action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Name name | string | Required | Name |
Sample request
{"name": "{{trigger.name}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Iterable Add to UserList (Bulk).
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Iterable Add to UserList (Bulk).
What does the Iterable Add to UserList (Bulk) action do in Iterable?
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.
What inputs does Iterable Add to UserList (Bulk) require?
Required: Name. 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 run history shows the failed step with its input and the error message Iterable returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Iterable Add to UserList (Bulk) support batch operations?
Run Iterable Add to UserList (Bulk) inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Iterable's rate limits.
More actions
Other Iterable actions.
Action
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.
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.
ActionSubscribe to List (Single User)
Single-user list subscription. For bulk operations (10+ users), use Add UserList which is much more efficient per-user.
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.