Set Contact Tags
getresponse.upsert_contact_tags
ActionEmailconnection required
Calls the GetResponse API with the connection's credentials.
Set the tags on a contact, replacing whatever tags it carried before.
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, 2 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 |
tag_ids Tag ids to set on the contact, comma-separated. These are ids from the List Tags node, not tag names. | string | Yes | — | — | m7E2,kL6Nh |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": "pV3r",
"tag_ids": "m7E2,kL6Nh"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
contact_id The contact that was tagged. | string | — |
tag_ids The tag ids that were sent. | array | — |
applied How many tag ids were sent. | number | — |
response GetResponse's response body for the call. | object | — |
{
"applied": 0,
"contact_id": "",
"response": {},
"tag_ids": []
}Notes
- This replaces the contact's tag set; it does not add to it.
See Set Contact Tags 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.