Book a demo

Create Contact

getresponse.create_contact
ActionEmailconnection required

Calls the GetResponse API with the connection's credentials.

Add a contact to a campaign (list). GetResponse queues the write and answers with no record, so this node reports that it was accepted.

Ask about GetResponseAll GetResponse nodesProvider API docs ↗

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, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
email
The contact's email address.
stringYes—email formatjohn.doe@example.com
campaign_id
The id of the campaign (contact list) to act on.
stringYes——V3J
name
The contact's name, up to 128 characters.
stringNo—≤ 128 charactersJohn Doe
day_of_cycle
Day to place the contact on in the campaign's autoresponder cycle. Leave blank to keep them out of the cycle.
stringNo——0
scoring
Initial contact score. GetResponse documents no upper bound.
numberNo—≥ 08
ip_address
The IPv4 or IPv6 address the contact signed up from, recorded as consent evidence.
stringNo——1.2.3.4
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"}

Example configuration

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

{
  "campaign_id": "V3J",
  "custom_field_values": {
    "kL6Nh": "18-35"
  },
  "day_of_cycle": "0",
  "email": "john.doe@example.com",
  "ip_address": "1.2.3.4",
  "name": "John Doe",
  "scoring": 8,
  "tag_ids": "m7E2,kL6Nh"
}

Output

One shape.

result

FieldTypeExample
queued
Always true on success: GetResponse accepted the contact for background processing. It is not on the list yet, and a double opt-in campaign holds it until the person confirms.
boolean—
email
The email address that was submitted.
string—
campaign_id
The campaign (list) the contact was submitted to.
string—
response
GetResponse's response body, which is empty for this accepted-and-queued call.
object—
{
  "campaign_id": "",
  "email": "",
  "queued": false,
  "response": {}
}

Notes

  • GetResponse answers with 202 Accepted and an empty body, so there is no new contact id to pass on. Read the contact back with List Contacts if a later step needs its id.
  • Adding an address that is already on the list is a 409 from GetResponse, not a silent update — use Update Contact for an existing contact.

Related GetResponse nodes

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

Book a technical demoTalk to sales