ActionCustomer.ioUpdated September 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.

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 run history shows the failed step with its input and the error message Customer.io returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Identify Person support batch operations?

Run Identify Person inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Customer.io's rate limits.

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