ActionSegmentUpdated May 2026

How do I update Segment user traits?

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

Use this action All 2 Segment 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
User ID userId	string	Required	User ID
Email email	email	Optional	The email address. Used as the recipient or identifier depending on context.
Name name	string	Optional	Name
Additional Traits traits	json	Optional	Additional Traits. (JSON object). e.g. "{ "plan": "pro", "company": "Acme" }"

Sample request

{
  "userId": "{{trigger.userId}}",
  "email": "e.g. user@example.com",
  "name": "{{trigger.name}}",
  "traits": "{ \"plan\": \"pro\", \"company\": \"Acme\" }"
}

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 Segment Identify User.

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

Google Sheets → Segment

2 Google Sheets triggers

HubSpot → Segment

18 HubSpot triggers

FAQ

Questions about Segment Identify User.

What does the Segment Identify User action do in Segment?

Upserts user traits that fan out to every connected destination (Mixpanel, HubSpot, Customer.io, etc.). The state update that drives downstream segmentation accuracy.

What inputs does Segment Identify User require?

Required: User ID. 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 Segment 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 Segment Identify User support batch operations?

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

More actions