Book a demo

List A Person's Activities

customer_io.list_customer_activities
ActionCRM & salesconnection required

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

Page through what a person did and what was sent to them, optionally narrowed to one activity type.

Ask about Customer.ioAll Customer.io nodesProvider API docs ↗

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

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

FieldTypeRequiredDefaultConstraintsExample
customer_id
The value that identifies the person, of the kind named by 'id_type'.
stringYes——ada@example.com
id_type
Which identifier 'customer_id' holds. Customer.io assumes 'id' when this is blank; 'email' and 'phone' work only where the workspace enables them as identifiers.
stringNo—one of "id", "email", "cio_id", "phone"—
activity_type
One Customer.io activity type to return, such as 'sent_email', 'clicked_email' or 'attribute_change'. Leave blank for every type.
stringNo———
limit
How many activities to return per page. Customer.io defaults to 10 and caps this at 100.
numberNo—1–100—
start
The paging token to continue from: the 'next' value a previous page returned.
stringNo———

Example configuration

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

{
  "customer_id": "ada@example.com"
}

Output

One shape.

result

FieldTypeExample
activities
One object per activity, newest first.
array—
activities[].id
The activity's id.
string—
activities[].type
What kind of activity it was.
string—
activities[].name
The event or message name, where there is one.
string—
activities[].timestamp
When it happened, as a Unix timestamp.
number—
activities[].delivery_id
The delivery it belongs to, if any.
string—
activities[].data
The activity's own payload.
object—
count
How many activities this page carries.
number—
next
The paging token for the next page; empty on the last one.
string—
{
  "activities": [
    {
      "data": {},
      "delivery_id": "",
      "id": "",
      "name": "",
      "timestamp": 0,
      "type": ""
    }
  ],
  "count": 0,
  "next": ""
}

Related Customer.io nodes

See List A Person's Activities 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.

Book a technical demoTalk to sales