Get Contact List
egoi.get_list
ActionEmailconnection required
Calls the E-goi API with the connection's credentials.
Read one contact list and its counters by id.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- E-goi
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- list_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 |
|---|---|---|---|---|---|
list_id E-goi list to act on; leave blank to use the list named on the connection. | string | No | — | — | 12345 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"list_id": "12345"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
list_id The list's E-goi id. | number | — |
internal_name The name shown inside the E-goi account. | string | — |
public_name The name shown to contacts on forms and footers. | string | — |
status Whether the list is active or blocked. | string | — |
created When the list was created, as an E-goi date-time. | string | — |
updated When the list was last changed, as an E-goi date-time. | string | — |
{
"created": "",
"internal_name": "",
"list_id": 0,
"public_name": "",
"status": "",
"updated": ""
}See Get Contact List run in a workflow.
In a technical demo we add the E-goi connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.