Delete Contact
getresponse.delete_contact
ActionEmailconnection required
Calls the GetResponse API with the connection's credentials.
Remove a contact from the account, optionally recording why they left.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- GetResponse
- Secret shape
- the API key, or {"api_key": "…"}, or {"access_token": "…"} for OAuth2
- Config it needs
- region, domain, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 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 |
|---|---|---|---|---|---|
contact_id The contact's GetResponse id, as returned by a list or search node. | string | Yes | — | — | pV3r |
message_id Id of the message the removal should be attributed to, so GetResponse credits the unsubscribe to that newsletter or autoresponder. | string | No | — | — | — |
ip_address The IP address the person unsubscribed from, recorded with the removal. | string | No | — | — | 1.2.3.4 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": "pV3r",
"ip_address": "1.2.3.4"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True once GetResponse confirmed the removal. | boolean | — |
contact_id The contact id that was removed. | string | — |
{
"contact_id": "",
"deleted": false
}See Delete Contact run in a workflow.
In a technical demo we add the GetResponse connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.