Search People

customer_io.search_customers

ActionCRM & salesconnection required

Calls the Customer.io API with the connection's credentials.

Find people with an audience filter, the same segment and attribute conditions the dashboard builds, and page through the identifiers it returns.

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

3 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
filter The audience filter, as a JSON object. Combine 'and', 'or' and 'not' around 'segment' and 'attribute' conditions. An empty filter is refused; Customer.io has nothing to match it against.	object	Yes	—	≥ 1 characters	{"and":[{"segment":{"id":7}}]}
limit How many people to return per page. Customer.io defaults to 50 and caps this at 1000.	number	No	—	1–1000	—
start The paging token to continue from: the 'next' value a previous page returned.	string	No	—	—	—

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

{
  "filter": {
    "and": [
      {
        "segment": {
          "id": 7
        }
      }
    ]
  }
}

One shape.

Field	Type	Example
identifiers One object per person, carrying id, email and cio_id.	array	—
identifiers[].id The person's own id, empty where they have none.	string	—
identifiers[].email The person's email address.	string	—
identifiers[].cio_id Customer.io's internal id for the person.	string	—
ids The same people as bare id strings; empty when none were returned.	array	—
count How many people this page carries.	number	—
next The paging token for the next page; empty on the last one.	string	—

{
  "count": 0,
  "identifiers": [
    {
      "cio_id": "",
      "email": "",
      "id": ""
    }
  ],
  "ids": [],
  "next": ""
}

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.