- Integrations
- /
- Iterable
- /
- Actions
- /
- Update Iterable User
ActionIterableUpdated May 2026
How do I update Iterable user attributes?
Short answer: Drop the "Iterable → Update Iterable 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 |
|---|---|---|---|
Email email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Data Fields (JSON) dataFields | string | Optional | {"firstName":"Jane","plan":"premium"} |
User ID (alternate key) userId | string | Optional | — |
Merge Nested Objects mergeNestedObjects | options | Optional | — |
Sample request
{"email": "e.g. user@example.com","dataFields": "{\"firstName\":\"Jane\",\"plan\":\"premium\"}","userId": "{{trigger.userId}}","mergeNestedObjects": "{{trigger.mergeNestedObjects}}"}
Returns
{"msg": "Success","code": "Success","params": {}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Update Iterable User.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Update Iterable User.
What does the Update Iterable User action do in Iterable?
Upserts user data fields (plan, country, signup_date, lifetime_value). The state-update hook for keeping audience segmentation accurate.
What inputs does Update Iterable User require?
Required: Email. 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 Update Iterable User support batch operations?
Yes. Run Update Iterable 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.
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.
Send update iterable user from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.