- Integrations
- /
- Segment
- /
- Actions
- /
- Segment Track Event
ActionSegmentUpdated May 2026
How do I push an event to Segment?
Short answer: Drop the "Segment → Segment Track Event" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Event Name event | string | Required | Event Name. Example: Order Completed |
Properties properties | json | Optional | Properties. (JSON object). e.g. "{ "revenue": 99.99, "currency": "USD" }" |
Sample request
{"userId": "{{trigger.userId}}","event": "e.g. Order Completed","properties": "{ \"revenue\": 99.99, \"currency\": \"USD\" }"}
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 Track Event.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Segment Track Event.
What does the Segment Track Event action do in Segment?
Sends a behavioural event that fans out to all configured destinations. The single-call hook for "log this server-side event everywhere" pattern that avoids per-destination integrations.
What inputs does Segment Track Event require?
Required: User ID, Event Name. 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 Track Event support batch operations?
Yes. Run Segment Track Event 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
Other Segment actions.
Send segment track event from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.