Forget Subscriber
mailerlite.forget_subscriber
ActionEmailconnection required
Calls the MailerLite API with the connection's credentials.
Request GDPR erasure of a subscriber and all of their recorded activity.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- MailerLite
- Secret shape
- the API token, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 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 |
|---|---|---|---|---|---|
subscriber_id The subscriber's MailerLite id. | string | Yes | — | — | 31982639460318841 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"subscriber_id": "31982639460318841"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
subscriber The subscriber record as it stood at erasure. | object | — |
message MailerLite's confirmation text for the request. | string | — |
subscriber_id The id the erasure was requested for. | string | — |
{
"message": "",
"subscriber": {},
"subscriber_id": ""
}Notes
- Erasure is scheduled, not immediate — MailerLite states the data is removed within 30 days, so the subscriber may still be readable straight afterwards.
See Forget Subscriber run in a workflow.
In a technical demo we add the MailerLite connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.