01 · trigger.webhook
Lead received
Signed production URL. The form posts, the run starts.
doneEverything an operator needs.
Nothing they don't.
Four surfaces, the canvas, runs, connections and docs, over one execution engine that treats reliability as a feature, not a plan tier. Every plan gets all of it.
A lead in, a text out,
and the receipt in between.
One bot the way it actually ran. A lead arrives, is qualified, lands in Podio, and the acquisitions manager is texted. The text timed out once, retried, and delivered. Every step is logged with its payload.
02 · logic.if
Qualified?
Branch on the fields. Anything that fails the rule routes to review.
true03 · podio.create_item
Record created
Fields mapped with expressions from the trigger payload.
done04 · ringcentral.send_sms
Manager texted
Timed out once. Per-step retry with wait-between sent it the second time.
retried ×1, delivered05 · run.complete
Receipt
Status, per-step timing and payloads kept in run history. Replay from any point.
0 errorsBatch and bundle.
Both.
Batch runs downstream once with the whole array: rollups, digests, bulk writes. Bundle runs it once per item: per-lead texts, per-row updates. Set it per bot, override it per node. No other tool gives you both.
Batch
Downstream runs once with the whole array.
Rollups, digests, bulk writes.
Bundle
Downstream runs once per item.
Per-lead texts, per-row updates. Set it per bot, override it per node.
Built to fail well.
Retries, dedicated error branches and Try/Catch are features of the engine. Every account gets them.
Per-step retriesMax tries and wait-between, set on any node.
Error outputsRoute failures down their own branch.
Try / CatchGuard a whole branch. Retry before the catch runs.
Run historyPer-step payloads, timing and errors, every run.
ReplayRe-drive a run from any point with pinned or modified data.
VersionsOne-click rollback to any prior version.
Four ways in.
Every bot starts with exactly one trigger.
trigger.webhook
Webhook
Signed test and production URLs. Custom responses.
trigger.schedule
Schedule
Recurrence rules, down to the minute.
trigger.manual
Manual
Fire from the bot page, or from Claude over MCP.
trigger.event
Inboxes and events
A new email, a text, a payment, a form. No plumbing.
AI where it earns its place.
Oppa, OpFlow's assistant, builds with you. AI steps run inside the flow.
OppaDescribe the bot and it's drafted on the canvas. Ask why a run failed and you get the cause and the fix.
AI stepClaude-backed. Plain text or forced-JSON replies, straight into the flow.
AI-written codeDescribe the step in English. The JavaScript is written fresh each run, shaped to the live input.
From ClaudeConnect OpFlow to Claude, Cowork or ChatGPT over MCP and run it from a sentence.