In OpFlow: Developer, then API and MCP. Read, write and run scopes.
Build automations by
talking to Claude.
OpFlow ships a native MCP server, so Claude, Cowork and ChatGPT build, run and debug your bots from a sentence. Connect once, then describe what you want. Every guide below is the same text the app shows inside Docs.
claude mcp add --transport http opflow https://flow.opscend.net/api/public/mcp --header "Authorization: Bearer opflow_YOUR_TOKEN"CopyAdd the server above to Claude, Cowork or Claude Code with your token.
"Build a bot that texts me when a lead comes in." It lands on the canvas, disabled, for you to check.
Every guide.
Grounded in the real engine. Nine guides, in the order you'll need them.
Build, run, and debug OpFlow bots by chatting with Claude — the MCP server + the OpFlow skill. The fastest way to use OpFlow.
Read02Getting startedFrom signup to your first running bot in about ten minutes.
Read03TriggersThe four ways a bot starts: webhook, schedule, manual, and platform events.
Read04ExpressionsReference any field from any prior step, resolved live at run time.
Read05Logic & codeBranching, loops, Try/Catch, and the JavaScript sandbox — the real engine.
Read06Runs & debuggingStep payloads, pinned data, run-from-here, retries, and replay.
Read07ConnectionsOAuth, API keys, credential folders, and multiple accounts per connector.
Read08SecurityEncryption at rest, per-workspace isolation, versioning, and SSO.
Read09Connectors referenceThe deep connectors and what they do — plus the HTTP escape hatch.
Read10Social kitOn-brand social posts from one renderer: Admin → Social kit for people, render_social_post for agents, a bot node for schedules. Plus the operating prompt for the social media agent.
ReadCommon shapes to start from.
Four bots most businesses build first. Ask Oppa for any of them and it's drafted.