Problem
Zapier, Make, and n8n connect your apps. Your business runs on the records inside them.
Webhook automation exists because the apps below it do not agree. A field changes in one app, a connector fails in another, and the business finds out when a customer, an invoice, or an approval is already wrong. The hidden cost of an automation estate isn't the seats — it's the cleanup.
contact.7741 status: pending contact_7741 stage: prospect row 7741 col B: €5,000 orders.7741 - status confirmed OMS
- ledger_entry €5,420 Finance
- contact.flag review CRM
The graph
Steps that act on the record itself.
A workflow reads like a flow chart the team can follow. Each step acts on the same customer, order, or invoice the form, the report, and the audit log already share. If a branch fails halfway through, the half that already ran undoes itself — no orphaned write left in a tool you forgot was connected.
order.created
amount > €5,000
oms.order.confirm gl.journal.post llm.classify.risk infobip.sms.send priority_score(model) Nodes
Different shapes, same plumbing underneath.
Whatever the step does, it reads the same records and writes them the same way. The plumbing is identical. What changes is what's inside the step.
Acts on the record itself.
First-class actions on every part of the platform — customers, orders, stock, invoices, content. The step writes to the same row the form and the report already read. A workflow that adds a customer, sets their credit limit, and assigns a warehouse is one change to the business, not three integrations to keep an eye on.
For the apps that still live outside.
Generic HTTP and webhook steps for the long tail. First-class steps for the integrations regional mid-market teams actually use — Pantheon for fiscal, Infobip for SMS, the major email providers. Every call still leaves an entry in the audit log, same as a step inside the platform.
Reads the business, not just the field.
Configure provider and prompt; the answer comes back into the workflow as structured data. The model sees the same records the platform reads — the customer, their orders, their ledger entries, their open tickets — not whichever blob a previous step happened to pass in. It runs with the calling user's permissions, not a system account.
For when the visual editor is the wrong shape.
Drop down to code when the chain needs logic the editor cannot express cleanly. Records, triggers, and approvals work the same as everywhere else. No deploy step on most subscriptions. The visual editor is the default — code is the exit, not a sibling product to learn and maintain.
LLM context
A model step is only as smart as what it can see.
In a webhook tool, the model sees whatever you piped into it — usually one field. Inside oozmi, it sees the same business the rest of the platform reads. The difference shows up the moment you ask it to make a judgment call.
Classify the credit risk for customer #88.
I only see name, email, last_order_total.
Not enough to go on — one transaction, no history, no segment, no ledger position to read.
Classify the credit risk for customer #88.
Reading customer, orders, ledger, tickets, segment…
Tier: medium. Two late payments inside a strategic relationship — recommend manual review before raising the limit.
Composition
What runs around the steps.
A workflow is more than the steps themselves. It is how a run starts, who signs off in the middle, and what happens when something fails. That layer is part of the product, not something the team has to build on the side.
-
Trigger
On a schedule, or the moment something changes in the platform — an order placed, a ticket closed, a margin rule tripped.
-
Branch
Conditions on real fields, parallel paths, loops. Every branch sees the same record state — no stale data passed between steps.
-
Approval
Wire any step to an approval ticket; the workflow pauses until someone signs off. The step runs as the approver, not a system account.
-
Commit
Approved steps go in together. If one fails, the rest undoes itself — no half-written customers, no half-posted invoices.
-
Audit
One entry in the audit log per step, tagged with the workflow that ran it. The same query reads writes by both people and workflows.
Boundary
Workflows is not the everyone tool.
The AI Builder pattern — anyone describes, the platform builds — is the right shape for analytics. For automations that change customer-facing state or financial state, the right shape is power users designing, with approvals attached. We keep the two surfaces deliberately distinct.
- The engine power users and department heads reach for.
- The right shape when the work changes a record — a customer, an order, an invoice.
- Designed with approvals attached, not bolted on.
- Records, approvals, and audit history governed by the same platform.
- An add-on, priced and packaged separately from the day-one platform.
- A self-service tool for end users — that is what AI Builder is for.
- The right shape for analytics, dashboards, or ad-hoc reports.
- A drop-in for Zapier when most of your automations live between apps that don't touch oozmi.
- A replacement for a developer team on edges that need real code — the JS step is the exit, not a hidden requirement.
- Included in every day-one subscription.
Thesis
Webhook automation exists because systems don’t.
Translation is the tax you pay when the things below you do not agree. When they agree, the tax disappears.
Zapier was a brilliant answer to a real problem. Every SaaS tool ships its own data shape and its own connector surface, so somebody has to be the translator. We chose a different starting point. CRM, finance, warehouse, HR, AI proposals, and the storefront are built on the same operating model. A workflow that touches three of them is one change applied across them, not three messages passed between three apps that each think they own the record.
The honest part of this: Workflows is a separate add-on. The platform’s day-one promise is that the records agree. Workflows is the engine you reach for when the team is ready to make that agreement act. We do not pretend it’s the everyone tool. We do not pretend it removes the need for a power user to think.
The disproof line The bet is that a unified model is worth more than the marketplace of connectors a webhook tool ships with. If your team’s automations live mostly outside the platform’s surface area — ad-network pixels, niche regional SaaS, vendor portals you cannot touch — the tradeoff goes the other way, and we owe you an honest read before we sell you the add-on.
Bring one process you’d otherwise script in Zapier.
Twenty-five minutes. We open the admin, build a workflow that updates three parts of the business in a single change, and walk you through the audit log entries that record it. If the approach holds up under your questions, we talk pilot.