Start free
ActionSegmentUpdated June 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.

Segment Track Event in Segment — start free All 2 Segment actions
Segment Track Event in Segment — 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
User ID
userId
stringRequiredUser ID
Event Name
event
stringRequiredEvent Name. Example: Order Completed
Properties
properties
jsonOptionalProperties. (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.

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

Other Segment actions.

Action
Segment Identify User
Upserts user traits that fan out to every connected destination (Mixpanel, HubSpot, Customer.io, etc.). The state update that drives downstream segmentation accuracy.
Segment Track Event in Segment — start free