Workflows
Automations you try first, that can ask before they act.
WorkflowsPlatform
One AI platform on the systems you already run
Platform overview Watch the tourAsk, see and act on one sample companySolutions · Operations
Ask which open orders are past their due date and get the count, the value and the list. Let a morning flow find them for you, try it first, and decide what goes out on one Waiting page.
Nobody approves their own proposal
One Waiting page holds the approvals, questions and failed runs from your flows and agents, with a count in the top bar.
The count, the value and the list of orders, each with its due date.
The open orders due that week, as a list you can sort and download.
The ready-made analysis "Stock that isn't moving" shows the money tied up by store and item, each line with what to do: sell it off, stop reordering, check demand or order less.
The runs page has a "Failed today" view. Failures are sorted by kind (a sign-in, a busy system, refused data, a limit), and a failed run can carry on from the step that failed.
It reads the scan and answers.
On Tarnwick Supply Co., sample data, with its order system connected through its web API (a flow cannot read a connected database today).
"Which open orders are past their due date, and what are they worth? Show their due dates." The answer: 37 orders, what they are worth, and the list with each due date. Ask "only the ones for Quellmark Foods" and it carries on.
37 orders, worth $184,920.
| Customer | Due date | Value |
|---|---|---|
| Quellmark Foods | 20 Oct | $12,840 |
| Fenwright Builders | 24 Oct | $9,615 |
| Lumora Hotels | 26 Oct | $8,930 |
A board "Late orders", by region and by status. A click on a row can open the order in your order system. Make it the page your team opens first.
A company owner builds a flow in the flow designer: every morning at seven it reads the open orders past their due date, writes a message for each one to its customer from that order's own figures, and waits at an "Ask someone first" step. Try it first: nothing is sent and nothing is changed.
The card waits on Waiting. Read each message as it will go out, and fix a line where the step allows. Approve many at once with one reason. Each request runs once, even if two people press together, and nobody approves their own proposal.
Read each message before it goes
Dear Quellmark Foods, your order SO-10482, due on 20 October, …
EditWhere wording must never change, a template step writes each message from your own words, with no AI at all.
| Order | Due date |
|---|---|
| SO-10482 | 20 Oct |
| SO-10455 | 24 Oct |
| SO-10471 | 26 Oct |
| To | Message |
|---|---|
| Quellmark Foods | Dear Quellmark… |
| Fenwright Builders | Dear Fenwright… |
| Lumora Hotels | Dear Lumora… |
Order PO-3307 has 40 units at $18.40; the invoice charges for 44. Flag a mismatch? This waits for a person.
So you know before the demo.
Automations you try first, that can ask before they act.
WorkflowsThe count, the value and the list.
AI AssistantLate orders in view, a click from the order itself.
DashboardsAlso behind these answers: AI Agents · History engine.
In the demo we connect one of your systems, and you ask the questions.