Create Contacts (Batch)
getresponse.create_contacts_batch
ActionEmailconnection required
Calls the GetResponse API with the connection's credentials.
Submit many contacts to one campaign (list) in a single call, reporting how many were accepted for processing.
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 |
|---|---|---|---|---|---|
campaign_id The id of the campaign (contact list) to act on. | string | Yes | — | — | V3J |
contacts The contacts to submit. Each entry needs an 'email' and may carry 'name', 'dayOfCycle', 'scoring', 'ipAddress', 'tags' and 'customFieldValues'. | array | Yes | — | array of object | [{"email":"john.doe@example.com","name":"John Doe"}] |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"campaign_id": "V3J",
"contacts": [
{
"email": "john.doe@example.com",
"name": "John Doe"
}
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
queued Always true on success: GetResponse accepted the batch for background processing rather than writing it immediately. | boolean | — |
submitted How many contacts this node sent. | number | — |
campaign_id The campaign (list) they were submitted to. | string | — |
emails The email addresses that were submitted, in order. | array | — |
response GetResponse's response body, which is empty for this accepted-and-queued call. | object | — |
{
"campaign_id": "",
"emails": [],
"queued": false,
"response": {},
"submitted": 0
}Notes
- The 202 response carries no per-contact result, so 'submitted' is what was sent, never a count of what landed on the list; individual contacts can still be rejected during processing.
See Create Contacts (Batch) 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.