Find People By Email
customer_io.find_customers_by_email
ActionCRM & salesconnection required
Calls the Customer.io API with the connection's credentials.
Look up every profile that holds an email address. A workspace can hold more than one, which is what a merge resolves.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Customer.io
- Secret shape
- {"site_id": "…", "api_key": "…", "app_api_key": "…"} — the Site ID and Track API key for the Track nodes, the App API key for the rest
- Config it needs
- region, workspace_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 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 |
|---|---|---|---|---|---|
email The email address to search for. The match is exact. | string | Yes | — | email format | ada@example.com |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"email": "ada@example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
results One object per matching person. | array | — |
results[].id The person's own id, when they have one. | string | — |
results[].email The person's email address. | string | — |
results[].cio_id Customer.io's internal id for the person. | string | — |
count How many profiles matched. | number | — |
{
"count": 0,
"results": [
{
"cio_id": "",
"email": "",
"id": ""
}
]
}See Find People By Email run in a workflow.
In a technical demo we add the Customer.io connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.