Use cases
Workflows teams run in production today.
Eight patterns with the steps, the tools and the numbers behind them. Each one is a starting point you can fork.
Support
ticket.created
Refunds that approve themselves, mostly
Classify refund tickets, check the charge history, refund duplicates under $200 automatically and ask a lead before anything bigger.
71% of refund tickets closed without a human touching them
Sales
form.submitted
Enrich and route every inbound lead in 40 seconds
Look up the company, score fit with an LLM against your ICP, write the first reply and assign an owner, before the visitor has closed the tab.
Speed-to-lead down from 3 hours to 40 seconds
Data
storage.object_created
Turn a folder of contracts into a searchable index
Extract text and clauses from every uploaded PDF, chunk and embed them, and keep the index in sync when files change or disappear.
12,400 contracts indexed overnight with zero lost files
Finance
mail.received
Invoices in, ledger entries out, with a human on exceptions
Read invoices from a shared inbox, match them to purchase orders, post clean ones to the ledger and send mismatches to finance with the reason attached.
Month-end close two days faster
Engineering
alert.fired
Triage incidents before the on-call engineer wakes up
When an alert fires, gather recent deploys, error spikes and related logs, summarise the likely cause and page the right team with a starting point.
Mean time to first useful message: 90 seconds
Ops
cron 0 7 * * MON
Weekly customer health reports that write themselves
Every Monday, pull usage, tickets and billing for each key account, write a short health summary and send it to the account owner.
42 account reports every Monday at 7:00
Ops
task.requested
Browser agents that finish long forms reliably
Drive supplier and government portals with a browser agent, saving each page as a checkpoint so a timeout on page nine doesn’t restart the whole form.
94% of portal filings completed on the first run
Engineering
model.candidate_published
Eval pipelines that don’t pay twice for a flaky call
Run every candidate prompt or model against your test set, score it with rubrics and graders, and only re-run the calls that actually failed.
38% lower eval spend per candidate model
Every integration is a typed function your agent can call.
Connect CRMs, billing, mail, chat, databases and browsers as typed tools. The types become the schema the model sees, so a bad tool call fails before it runs, not after.
What engineers wrote in the commit that switched them over.
Get started
Don’t see your workflow?
Tell us what you’re building. An engineer, not a sales rep, will reply with a sketch of the steps within a working day.