List Contacts

egoi.list_contacts
ActionEmailconnection required

Calls the E-goi API with the connection's credentials.

List a page of the contacts in one E-goi list, with optional filters.

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

8 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
list_id
E-goi list to act on; leave blank to use the list named on the connection.
stringNo——12345
limit
How many rows to return in this page; E-goi returns 10 when it is left blank.
numberNo—1–1000—
offset
How many rows to skip before the first one returned, for paging.
numberNo—≥ 0—
email
Return only contacts whose email address matches this value.
stringNo—email formatjane@example.com
first_name
Return only contacts whose first name matches this value.
stringNo———
last_name
Return only contacts whose last name matches this value.
stringNo———
cellphone
Return only contacts whose mobile number matches this value.
stringNo———
phone
Return only contacts whose landline number matches this value.
stringNo———

Example configuration

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

{
  "email": "jane@example.com",
  "list_id": "12345"
}

Output

One shape.

result

FieldTypeExample
items
The rows E-goi returned for this page.
array—
count
How many rows this page carried.
number—
total_items
How many rows match in total, across every page.
number—
{
  "count": 0,
  "items": [],
  "total_items": 0
}

See List Contacts 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.