Signal
Product analytics that explains itself. See what moved, and the event that moved it.
Flow · Workflow automation
Requests in. Decisions out. Nobody chasing anybody.
Flow takes the work that arrives by email, form or webhook, applies the rules you describe in plain steps, and sends each item to the right person with a deadline attached. Every run is logged, so you can see exactly what happened and why.
TriggerNew ticket tagged “refund” in Desk
ConditionOrder amount above your limit
Yes → approvalFinance lead approves within 4 h
No → actionRefund issued automatically
ActionReply to customer, close ticket
Recent runs
- Ticket 2041Completed
- Ticket 2040Waiting approval
- Ticket 2038Completed
- Ticket 2035Failed · retry
Why it failed: the payment provider timed out. Flow retried twice and paused the run for review.
Where teams use Flow
Built for the work that keeps coming back.
Finance approvals
Refunds, expenses and purchase requests go to the right approver based on amount, team and policy.
Employee onboarding
One HR form opens the IT ticket, queues access and reminds the manager before day one.
Vendor invoices
Invoices that match the purchase order move on; mismatches go to Accounts with the context attached.
How it works
Three steps to your first result.
- 01Connect where work arrivesEmail, forms and your own app’s webhooks.
- 02Describe the rules in plain stepsConditions, owners, approvals and deadlines.
- 03Watch each run and fix what’s stuckEvery run is logged with who did what, and failures explain themselves.
Questions about Flow
Do I need to write code?
No. Rules are built from plain steps. Developers can also send work in through webhooks.
What happens when a step fails?
The run pauses with the reason shown, retries where it is safe to, and waits for a person where it isn’t.
Works on the same account as
Desk
Customer support with drafted answers your agents review, edit and send.