Forget User
iterable.forget_user
ActionEmailconnection required
Calls the Iterable API with the connection's credentials.
Erase a user under GDPR and block Iterable from collecting their data again.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Iterable
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- region, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
email The email address that identifies the user. Provide this or 'user_id'. | string | No | — | email format | — |
user_id The userId that identifies the user. Provide this or 'email'. | string | No | — | — | — |
- At least one of email, user_id must be set.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
code Iterable's response code, 'Success' when the call was accepted. | string | — |
msg The human-readable message Iterable returned. | string | — |
params Any extra detail Iterable attached to the response. | object | — |
{
"code": "",
"msg": "",
"params": {}
}Notes
- Irreversible from a workflow: the identifier stays blocked until someone calls Iterable's unforget endpoint.
- Email-based projects must forget by email; userID-based projects by userId.
See Forget User run in a workflow.
In a technical demo we add the Iterable connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.