Update Contact

getresponse.update_contact
ActionEmailconnection required

Calls the GetResponse API with the connection's credentials.

Change a contact's name, score, tags, custom fields, autoresponder day or campaign, and return the updated record.

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

8 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
contact_id
The contact's GetResponse id, as returned by a list or search node.
stringYes——pV3r
name
New name for the contact, up to 128 characters.
stringNo—≤ 128 characters—
campaign_id
Move the contact to this campaign (list).
stringNo——V3J
day_of_cycle
Move the contact to this day of the campaign's autoresponder cycle.
stringNo———
scoring
New contact score. Send 0 to clear the score.
numberNo—≥ 08
note
A note to store on the contact.
stringNo———
tag_ids
Tag ids to attach, comma-separated. These are ids from the List Tags node, not tag names.
stringNo——m7E2,kL6Nh
custom_field_values
Custom field values, either as GetResponse's own list of {'customFieldId': ..., 'value': [...]} entries or as a flat {'customFieldId': 'value'} object.
objectNo——{"kL6Nh":"18-35"}
  • At least one of name, campaign_id, day_of_cycle, scoring, note, tag_ids, custom_field_values must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "campaign_id": "V3J",
  "contact_id": "pV3r",
  "custom_field_values": {
    "kL6Nh": "18-35"
  },
  "scoring": 8,
  "tag_ids": "m7E2,kL6Nh"
}

Output

One shape.

result

FieldTypeExample
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": ""
}

Notes

  • GetResponse updates by POSTing to the contact's own URL; there is no PUT.
  • Tags and custom field values are replaced wholesale by what you send, not merged with what the contact already has.

See Update 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.