Search Contacts
egoi.search_contacts
ActionEmailconnection required
Calls the E-goi API with the connection's credentials.
Find a contact across every list on the account by one of its channels.
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
2 fields, 1 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 |
|---|---|---|---|---|---|
contact The email address or phone number to look for, in full. | string | Yes | — | — | jane@example.com |
search_type Which channel the value above belongs to; E-goi searches emails by default. | string | No | one of "email", "cellphone", "phone" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact": "jane@example.com",
"search_type": "email"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The matches, each with a contact_id and a list_id. | array | — |
count How many matches E-goi returned. | number | — |
total_items Always empty here: E-goi returns no total for a contact search. | number | — |
{
"count": 0,
"items": [],
"total_items": 0
}See Search 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.