Route a purchase request to the right approver
A request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.
Gmail
Notion
Slack
5 steps3 integrationsRuns on demand
Requests arrive by message and get lost. What it costs while the work is still done by hand.
- 01Requests arrive by message and get lost.
- 02Nobody remembers who signs off above which amount.
- 03The requester chases; the approver never saw it.
- Read request$4,200 · design software
- Pick approverover $2,000 · finance lead
- Log requestcreate_page · purchases db
- Alert approverpost_message · with amount
- Log decisionapproved · Tue 14:02
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the request.Gmail
- 02Determine the approver from the amount and the category.ModuleX
- 03Record the request in your tracker.Notion
- 04Notify the approver with the details in the message.Slack
- 05Record the decision when it comes back.Notion
The workflow is an editable graph. Reading runs freely; record the request in your tracker waits for your opt-in approval until you loosen it. The graph is the receipt.
Routed, recorded, decided. Paste this into ModuleX chat, or hit Use this workflow.
route a purchase request to the right approver: read the request; determine the approver from the amount and the category; record the request in your tracker; notify the approver with the details in the message. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Route a purchase request to the right approver. A request that reached the right person, with a record of who approved what.
- notion · create_page
- slack · post_message
A request that reached the right person, with a record of who approved what.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Categorise card spend without the month-end scrambleA categorised transaction list plus a short list of the entries that genuinely need a human. Built for a finance lead reconciling a month of transactions from memory.
Assemble the month-end close digestA month-end digest in a consistent shape, assembled from the systems of record. Built for a finance team that rebuilds the same summary every month by hand.- Reconcile payouts against your ledgerA reconciliation summary that names the specific rows to look at, not just a total that is off. Built for whoever matches the payment processor to the accounting sheet each week.
About this use case.
No. It routes and records; the approval is a person's.