Built for Operations

A real bot engine behind a canvas an operator
can drive. Every number below is OpFlow's own, read
from its database, running live operations since July 2026.

Time Saved
Manual Work Done for You

days

and 4 hours 7 minutes, since July 2026
2 min a message, 3 a record, 5 an AI reply

Runs Completed
Successful Runs to Date

K

Bot runs that finished
clean since July 2026

Bots Live
Running Right Now

On schedules, webhooks,
inboxes and events

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.

01 · trigger.webhook
Lead received

Signed production URL. The form posts, the run starts.

done
02 · logic.if
Qualified?

Branch on the fields. Anything that fails the rule routes to review.

true
03 · podio.create_item
Record created

Fields mapped with expressions from the trigger payload.

done
04 · ringcentral.send_sms
Manager texted

Timed out once. Per-step retry with wait-between sent it the second time.

retried ×1, delivered
05 · run.complete
Receipt

Status, per-step timing and payloads kept in run history. Replay from any point.

0 errors

The engine is not
a plan tier.

Every account gets the whole engine. We gate scale, never capability.

BranchingIf and Switch routing, as many paths as the flow needs.
LoopsThe whole array, or one item at a time. Parallel when you want it.
Code stepsSandboxed JavaScript, or describe the step in English and AI writes it.
ExpressionsAny field from any prior step, resolved live.
RetriesPer-step retry with wait-between, on any node.
Try / CatchGuard a whole branch. A dedicated error output routes the failure.
WebhooksReliable delivery with a full log.
SchedulesDown to the minute.
VersioningEvery change captured. Roll back to any point.
Run historyPer-step payloads, timing and errors. Replay from any point.
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.

Running real operations
since July 2026.

Read from OpFlow's own database on 30 September 2026. Not projections.

K

Bot runs to date, 6,005 of them in the last 24 hours.

Bots enabled right now, on schedules, webhooks, inboxes and events.

K

Runs started by an AI client over MCP. 91.6% of them succeeded.

s

90th-percentile completed run. The median is 722 ms.

As deep as
the API goes.

68 apps and 4,285 operations in the catalog, built to the depth of each API. The HTTP node reaches anything with a REST API.

Telnyx1,254 ops
Stripe795 ops
RingCentral504 ops
Pinterest264 ops
Discord243 ops
Telegram195 ops
X184 ops
Google Business93 ops
YouTube86 ops
Google Chat68 ops
Google Sheets62 ops
Podioconnector
Gmailconnector + trigger
Google Driveconnector
Google Calendarconnector
Airtableconnector
Notionconnector
ManyChatconnector
Facebookconnector
Instagramconnector
Threadsconnector
TikTokconnector
Tremendousconnector
HTTPany REST API

Plus the Opscend-native nodes: OpVault, OpSite pages and forms, AI, code, database, respond, and twelve logic nodes.

Built for agents, too.

OpFlow ships a native MCP server. Claude can build, validate, run and inspect bots in conversation, from Claude Code, Desktop or Cowork.

SESSION · CONNECTMCP · STREAMABLE HTTP
$ claude mcp add --transport http opflow https://flow.opscend.net/api/public/mcp \
    --header "Authorization: Bearer opflow_…"
added opflow · 11 tools

› build a bot: when a lead form posts, qualify it, create the Podio item, text the manager
validate_bot_graph · ok · 5 nodes · 0 warnings
create_bot · 9b1f… · disabled until you enable it

Agents defined on the platform, each with its own files and bots. Activation stays a human decision.

Every run starts
with a signal.

550 trigger operations in the catalog. Four families, one REST API, one MCP server.

trigger.webhook
Webhook

Signed test and production URLs in. Custom responses out.

trigger.schedule
Schedule

Recurrence rules, down to the minute.

trigger.manual
Manual

Fire it from the bot page, or from an API call.

gmail · ringcentral · …
App events

An email received, an SMS in, a Stripe event. Polling covers the inboxes that never push.

Waitlist only,
for now.

OpFlow runs real operations every minute for the businesses it was built inside. New accounts open one at a time while that stays true. Leave a name and an email; a person reads the list.

Already invited? Sign in.

Request access

Name and email. That is the whole form.

No card, no trial timer, no drip sequence. A confirmation lands in your inbox; the invitation follows if it fits.

Join the line