ActionSegmentUpdated September 2026
How do I push an event to Segment?
Short answer: You can segment track event in Segment by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Segment Segment Track Event action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 run history shows the failed step with its input and the error message Segment 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 Segment Track Event support batch operations?
Run Segment Track Event 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 Segment's rate limits.
More actions