Segment
Segment customer data infrastructure
Segment (now Twilio Segment) is the customer data platform (CDP) — capture user events and identities once via the Segment SDK or API, fan out to 350+ destinations (analytics tools, CRMs, email tools, data warehouses) without integrating each separately. Tiny Command exposes two actions, no triggers (Segment is the destination for events; for "react to a behavioural cohort" workflows, use Segment's Personas to push to downstream destinations): Identify User (upsert user properties — Segment's user-state update that fans out to all destinations), Track Event (push a behavioural event with optional properties — fans out to every destination subscribed to that event). The connection uses a Segment write key from the source's settings. The fan-out value is significant — instead of integrating Mixpanel + HubSpot + Customer.io + Snowflake separately for every event, Segment captures once and distributes. For workflows that want to add server-side tracking that complements client-side SDK events, this is the path.
Do anything Segment can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| 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 | 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. |
Pre-built Segment workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Segment once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Segment field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Segment integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Segment to Tiny Command?
What Segment triggers does Tiny Command support?
What Segment actions can I run from a workflow?
Is the Segment integration real-time?
Do I need to write code to use Segment with Tiny Command?
How much does the Segment integration cost?
More analytics apps people connect.
Same category as Segment, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Segment.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
