Build automations by talking to Claude.
OpFlow ships a native MCP server and an installable skill, so Cowork and Claude Code build, run, and debug your workflows from a sentence. Connect once, then just describe what you want.
claude mcp add --transport http opflow https://flow.opscend.net/api/public/mcp --header "Authorization: Bearer opflow_YOUR_TOKEN"In OpFlow: Developer → API & MCP — read, write, run scopes.
Add the HTTP server above to Cowork / Claude Code with your token, then install the skill.
“Build a workflow that texts me when a lead comes in.”
All the guides
References for building on OpFlow — grounded in the real engine, honest about what's live and what's still hardening.
Build, run, and debug OpFlow workflows by chatting with Claude — the MCP server + the OpFlow skill. The fastest way to use OpFlow.
Read →From signup to your first running workflow in about ten minutes.
Read →The four ways a workflow starts: webhook, schedule, manual, and platform events.
Read →Reference any field from any prior step, resolved live at run time.
Read →Branching, loops, Try/Catch, and the JavaScript sandbox — the real engine.
Read →Step payloads, pinned data, run-from-here, retries, and replay.
Read →OAuth, API keys, credential folders, and multiple accounts per connector.
Read →Encryption at rest, per-workspace isolation, versioning, and SSO.
Read →The deep connectors and what they do — plus the HTTP escape hatch.
Read →Recipes
Common shapes to start from — swap in your own tools and conditions.