Start free
ActionCustomer.ioUpdated June 2026

How do I update Customer.io person attributes?

Short answer: You can identify person in Customer.io by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Customer.io Identify Person action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Identify Person in Customer.io — start free All 4 Customer.io actions
Identify Person in Customer.io — start free
Inputs

The fields this action accepts.

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

FieldTypeRequiredDescription
Identifier
identifier
stringRequiredUnique identifier — typically email or internal user ID
Email
email
stringOptionalEmail. e.g. "user@example.com"
First Name
first_name
stringOptionalFirst Name. e.g. "John"
Last Name
last_name
stringOptionalLast Name. e.g. "Doe"
Plan
plan
stringOptionalCustomer plan/tier for segmentation
Created At
created_at
stringOptionalUnix 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.

Gmail → Customer.io
1 Gmail triggers
Slack → Customer.io
13 Slack triggers
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. TinyCommand handles Customer.io's rate limits automatically so you don't have to throttle manually.
More actions

Other Customer.io actions.

Action
Delete Person
Hard-deletes the person and history. Irreversible — used for GDPR right-to-erasure compliance flows. For soft-removal use suppression list or unsubscribe.
Action
Send Transactional Email
Fires a transactional template (designed in Customer.io UI) at a specific recipient with merge data. For "password reset, order confirmation, receipt" workflows where the email content is reviewed in CIO but the trigger is external.
Action
Track Custom Event
Pushes a behavioural event into Customer.io's event store. Journeys and campaigns can trigger on these. The standard hook for "server-side action happened → fire CIO event to start the matching journey".
Identify Person in Customer.io — start free