List Custom Fields
getresponse.list_custom_fields
ActionEmailconnection required
Calls the GetResponse API with the connection's credentials.
List the account's custom fields so a contact write can reference them by 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
5 fields, none 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 |
|---|---|---|---|---|---|
name Only return custom fields whose name matches this value. | string | No | — | — | — |
sort_order Direction to sort custom field names in. | string | No | — | one of "ASC", "DESC" | — |
fields Comma-separated list of properties to return instead of the whole record. The id is always included. | string | No | — | — | contactId,email,name |
page Which page of results to fetch. GetResponse counts from 1. | number | No | 1 | ≥ 1 | 1 |
per_page How many records to ask GetResponse for in one page. | number | No | 100 | 1–1000 | 100 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": "contactId,email,name",
"page": 1,
"per_page": 100
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records on this page, exactly as GetResponse returned them. | array | — |
returned How many records this page contains. | number | — |
page The page number that was requested. | number | — |
per_page The page size that was requested. | number | — |
has_more True when this page came back full, so another page probably follows. GetResponse reports the exact total only in a response header, which this node does not read. | boolean | — |
{
"has_more": false,
"items": [],
"page": 0,
"per_page": 0,
"returned": 0
}See List 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.