Get Contact
getresponse.get_contact
ActionEmailconnection required
Calls the GetResponse API with the connection's credentials.
Fetch one contact by its GetResponse id, with its campaign and score.
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
2 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 |
fields Comma-separated list of properties to return instead of the whole record. The id is always included. | string | No | — | — | contactId,email,name |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": "pV3r",
"fields": "contactId,email,name"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
contact The contact record GetResponse returned, unchanged. | object | — |
contact_id The contact's GetResponse id. | string | — |
email The contact's email address. | string | — |
name The contact's name, or null when it has none. | string | — |
campaign_id The id of the campaign (list) the contact belongs to. | string | — |
{
"campaign_id": "",
"contact": {},
"contact_id": "",
"email": "",
"name": ""
}See Get 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.