Set Contact Custom Fields

getresponse.upsert_contact_custom_fields
ActionEmailconnection required

Calls the GetResponse API with the connection's credentials.

Set custom field values on a contact by custom field id.

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.

FieldTypeRequiredDefaultConstraintsExample
contact_id
The contact's GetResponse id, as returned by a list or search node.
stringYes——pV3r
custom_field_values
Values to set, either as GetResponse's own list of {'customFieldId': ..., 'value': [...]} entries or as a flat {'customFieldId': 'value'} object. Ids come from the List Custom Fields node.
objectYes——{"kL6Nh":"18-35"}

Example configuration

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

{
  "contact_id": "pV3r",
  "custom_field_values": {
    "kL6Nh": "18-35"
  }
}

Output

One shape.

result

FieldTypeExample
contact_id
The contact that was written to.
string—
custom_field_ids
The custom field ids that were sent.
array—
applied
How many custom fields were sent.
number—
response
GetResponse's response body for the call.
object—
{
  "applied": 0,
  "contact_id": "",
  "custom_field_ids": [],
  "response": {}
}

See Set Contact Custom Fields 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.