ActionCustomer.ioUpdated May 2026

How do I update Customer.io person attributes?

Short answer: Drop the "Customer.io → Identify Person" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Customer.io actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Identifier identifier	string	Required	Unique identifier — typically email or internal user ID
Email email	string	Optional	Email. e.g. "user@example.com"
First Name first_name	string	Optional	First Name. e.g. "John"
Last Name last_name	string	Optional	Last Name. e.g. "Doe"
Plan plan	string	Optional	Customer plan/tier for segmentation
Created At created_at	string	Optional	Unix timestamp of when the customer signed up

Sample request

{
  "identifier": "user@example.com",
  "email": "user@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "plan": "e.g. pro"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Identify Person.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Customer.io

2 Google Sheets triggers

HubSpot → Customer.io

18 HubSpot triggers

FAQ

Questions about Identify Person.

What does the Identify Person action do in Customer.io?

Upserts person-level attributes (plan, country, signup_date, lifetime_value). The state update that drives segmentation and journey targeting. For "external state change → reflect in CIO for accurate audience filtering" sync.

What inputs does Identify Person require?

Required: Identifier. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Customer.io returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Identify Person support batch operations?

Yes. Run Identify Person inside a Loop node to process arrays. Tiny Command handles Customer.io's rate limits automatically so you don't have to throttle manually.

More actions