Describe, Deploy, OwnWorkflow automation your agent writes, compiled into your Cloudflare account.

Q: Can my coding agent use this?

Yes. Run "npx -y n2c-mcp@latest install" to give Claude Code, Cursor, Codex, Windsurf, VS Code, Zed or any other MCP client 28 tools to browse schemas, build workflows, preview compiled Workers, test nodes, and deploy. It works on every plan, including free. Deploys require your approval by default.

Q: Can an agent call a workflow I already deployed?

Yes. Add an MCP Tool trigger to your workflow. The deployed Worker exposes an MCP endpoint that coding agents can discover and call directly using a bearer token you control. If the workflow has a wait, a delay or an approval step, the call returns the run's id and the fact that it started, not its result, because a durable run can park for days.

Your agent writes it over MCP. We validate it, recompile it to plain TypeScript and, by default, deploy only when you approve. It keeps running with us removed.

Start free

Not a developer? Describe it in plain English in the editor How it works

free plan · MCP server included · needs a free Cloudflare account

drag to spin

How it works

From canvas to cloud in minutes.

01Author

02Review

03Deploy

04Call back

AuthorSTEP 01 OF 04

Your agent writes it over MCP, or you build it on the canvas or in plain English.

Integrations

Yes, it connects to that.

SlackOpenAIStripeGitHubNotionAirtableHubSpotSupabaseGoogle SheetsAnthropicActiveCampaignApache KafkaAsanaAWSCalendlyClickUpCustom ModelDiscordElasticsearchEmail TriggerFacebookFirebaseFreshdeskGhostGitLabGmailGoogle AnalyticsGoogle BigQueryGoogle CalendarGoogle DocsGoogle DriveGoogle Gemini ModelIntercomJiraJotformMailChimpMatrixMattermostMCP Client ToolMessageBirdMonday.comPipedriveRedisSendGridShopifySnowflakeTelegramTrelloTwilioTypeformVonageWebflowWhatsAppWooCommerceWordPressYouTubeAnd more

Pre-wired for the modern stack.

Browse all 154 integrations →

What you build

Infrastructure-grade workflows.

Our analyzer reads your graph's shape and automatically assigns the correct Cloudflare compile target under the hood.

Refunds a human has to approve

Human in the loop

compiles to Cloudflare Workflow

A support agent that files its own tickets

AI agent

compiles to Email Worker

The 9am revenue digest

compiles to Scheduled Worker

Ask your docs, in chat

RAG

compiles to Worker

Form to CRM, without the copy-paste

compiles to Worker

Nightly sync into the warehouse

compiles to Cloudflare Workflow

GitHub issue triage & auto-reviewer

DevOps

compiles to Worker

Instant payment webhook & ledger sync

compiles to Cloudflare Workflow

Auto-scheduler & calendar invite agent

compiles to Email Worker

Browse workflow templates →

Demo

Watch an agent build one.

claude code · mcp

list_node_types233 nodes · 18 groups
get_node_schemas5 types
create_workflowrefund_approval
update_workflow7 nodes · 6 edges
validate_workflowok · 0 errors · 13.7 KB gzip

The agent writes graph JSON, never a script. What it hands us is data, which is the only reason the next three steps are possible at all.

Refund approval0/7 nodes

four gates · none the agent can skip

Structural validator
The agent writes graph JSON, never a script. The shape is checked before anything else runs.
Server-side recompile
Deploy always recompiles from the saved graph. It never trusts a script from the browser, or from the agent.
Reviewable diff
Versioned output you can read line by line, and roll back to.
Your approval
A round-trip to you, in the editor. On by default on every plan; on Pro you can let one connected agent deploy without asking — your setting, never the agent's.

deploy approval

src/index.ts

266 lines13.7 KB gzip

// Compiled by Nodes2Cloud — https://nodes2cloud.com
// Workflow: "Refund approval" (ID: "refund_approval")
// Target: Cloudflare Workflow

import { WorkflowEntrypoint } from "cloudflare:workers";

function __ccRpcResult(id, result) { return Response.json({ jsonrpc: "2.0", id, result }); }

function __ccRpcError(id, code, message, status) {
  return Response.json({ jsonrpc: "2.0", id, error: { code, message } }, { status: status ?? 200 });
}

async function __ccToolResult(value) {
  let unwrapped = value === undefined ? null : value;
  if (unwrapped instanceof Response) {
    const body = await unwrapped.clone().text();
    try { unwrapped = JSON.parse(body); } catch { unwrapped = body; }
  }
  const text = typeof unwrapped === "string" ? unwrapped : (JSON.stringify(unwrapped) ?? "null");
  const structured =
    unwrapped !== null && typeof unwrapped === "object" && !Array.isArray(unwrapped)
      ? { structuredContent: unwrapped }
      : {};
  return { content: [{ type: "text", text }], ...structured };
}

export class N2CWorkflow extends WorkflowEntrypoint {
  async run(event, step) {
    const env = this.env;
    const ctx = {
      input: event.payload,
      output: {},
      nodes: {},
      env,
      execution: {
        id: crypto.randomUUID(),
        startedAt: new Date().toISOString(),
        durationMs: 0,
        retryCount: 0,
        currentStep: "",

deployworking

reading saved graph
recompiling server-side
bundling worker
uploading to your account
live

Target: Cloudflare Workflow
Bundle: 13.7 KB gzip
Emitted: 266 lines
Steps, all paths: 4

Compiled ahead of time, not interpreted at run time. There is no runtime of ours in your account — the Worker is the workflow.

your cloudflare account

CREDENTIAL_ASKSecret
CC_RESUME_SECRET_APPROVALSecret
CREDENTIAL_REFUND_APPROVEDSecret
CREDENTIAL_REFUND_NOWSecret

4 secrets, 3 subrequests, and a step budget the compiler worked out before you shipped it.

The compiler counts 4steps across both paths, so Cloudflare’s free plan covers at least 750 runs a day against its 3,000 steps-a-day budget. You pay Cloudflare for the rest, at their published rate.

agent · tools/listscanning

refund_approval

Starts a Stripe refund for a payment. Refunds over $500 first ask in Slack and wait up to 24 hours for a decision, so the call answers with the run id, not the refund. To answer, send the run a refund_decision event with {"approved": true} or {"approved": false}.

payment_intentstringrequired
amount_centsintegerrequired
reasonstringrequired

One workflow is one tool, so each one is approved, versioned and revoked on its own. Authentication is a bearer token you set, on by default.

tools/call

{
  "name": "refund_approval",
  "arguments": {
    "payment_intent": "pi_3Q4x…",
    "amount_cents": 72000,
    "reason": "It arrived damaged"
  }
}

response

startedinstanceId 3f6c2a1e-9b4d-4c7a-…

Not a result. This workflow can wait for a human, so every call answers with the run it started — even a small refund that goes straight through. A durable run can park for days and no HTTP request waits that long. Workflows with no wait anywhere in them answer with their result.

#billing — Refund $720 on pi_3Q4x…? It arrived damaged. Tell your agent yes or no within 24 hours. The run is parked until your agent sends your answer back.

Asks before deploying: by default
Can bypass the compiler: no
Runs on: your account
Available on: every plan

Control

Control at your fingertips.

Your agent can build, check and propose. By default, nothing reaches your Cloudflare account until you say yes. AI is never a deploy bypass.

Your agent never sees a credential
No endpoint returns a credential's value, not to an agent and not to you. A test run can only send a credential to that service's own API.
Encrypted for your account alone
AES-256-GCM under a key derived for your account. The master key is never stored in our database.
Keys we cannot use
Lock a credential with a passkey or passphrase. We hold nothing that can unwrap it, so deploying it needs you there.
Permissions per agent
Choose what each connected agent may do and which workflows it may touch, and cap its daily actions. It never gets more than its sign-in allowed.
Callable tools need a token
A workflow your agent can call requires a bearer token by default. A blank one will not compile.
We store no execution data
In production, data moves between your Cloudflare account and your services. Test runs, live debug and agent tool calls pass through us in transit and are written nowhere.

Read the full security model →

Cost

Scale your automations, not your bill.

Reasonable pricing, so you can allocate budget to what matters. Our flat fee stays predictable while executions run directly on your Cloudflare account at wholesale compute rates.

Monthly cost · both axes logarithmic100,000 runs

YouA leading per-task platformHover or drag the chart

The shaded gap is what a per-task platform would have cost instead.

Against a per-task platform

22×

less, at this volume — $500 a month against $23.

Nodes2Cloud Pro: $18flat and just once
Cloudflare requests: $5their bill, your account
Cloudflare steps · up to 4/run: $0within the allowance

See every plan →

Questions

The questions you were going to ask anyway.

Yes. Run:npx -y n2c-mcp@latest installto give Claude Code, Cursor, Codex, Windsurf, VS Code, Zed or any other MCP client 28 tools to browse schemas, build workflows, preview compiled Workers, test nodes, and deploy. It works on every plan, including free. Deploys require your approval by default.

No. Describe what you need in plain English and the assistant creates the steps for you to review, or build by dragging nodes on the canvas. Nothing goes live until you approve it. The one thing you set up yourself is a free Cloudflare account, connected once.

You need an account, not expertise. Your Workers run in your own Cloudflare account (the free plan works), and Nodes2Cloud provisions the databases, storage buckets, queues, and secrets they need for you.

No. Cloudflare's free tier includes 100,000 Worker requests per day, D1 databases, and Workflows. If your volume expands, you pay Cloudflare directly with no markup from us.

Yes. Add an MCP Tooltrigger to your workflow. The deployed Worker exposes an MCP endpoint that coding agents can discover and call directly using a bearer token you control. If the workflow has a wait, a delay or an approval step, the call returns the run's id and the fact that it started, not its result, because a durable run can park for days.

233 nodes are supported out of the box, connecting to 154 external services. You can also connect to any REST API using the HTTP Request node or run custom JavaScript via the Code node.

Not in production. Deployed workflows run in your Cloudflare account, so their payloads go straight between your Worker and your services. Test runs, live debug sessions and agent tool calls made through our MCP server pass through us in transit; none of it is stored. Your API keys are encrypted under a key derived for your account, and the master key lives in Cloudflare's secret store, never in our database.

Your automations continue running uninterrupted because they live in your Cloudflare account. You can also export your project as standard TypeScript source code and deploy it from your own CI pipeline at any time.

Not today. We plan to release the compiler and node libraries under Apache-2.0 in the future, but Nodes2Cloud is currently proprietary.

free plan · MCP included

Let your agent ship it.You approve what goes live.

Start freeFor your coding agent

Tell us one automation you need, and we’ll build it with you.Email the founders →

Describe, Deploy, OwnWorkflow automation your agent writes, compiled into your Cloudflare account.

From canvas to cloud in minutes.

Yes, it connects to that.

Infrastructure-grade workflows.

Refunds a human has to approve

A support agent that files its own tickets

The 9am revenue digest

Ask your docs, in chat

Form to CRM, without the copy-paste

Nightly sync into the warehouse

GitHub issue triage & auto-reviewer

Instant payment webhook & ledger sync

Auto-scheduler & calendar invite agent

Watch an agent build one.

Control at your fingertips.

Your agent never sees a credential

Encrypted for your account alone

Keys we cannot use

Permissions per agent

Callable tools need a token

We store no execution data

Scale your automations, not your bill.

The questions you were going to ask anyway.

01Can my coding agent use this?

02Do I need to be a developer?

03Do I need to know Cloudflare to use this?

04Do I need a paid Cloudflare account?

05Can an agent call a workflow I already deployed?

06Do you have the integrations I use?

07Can you see my data?

08What happens if Nodes2Cloud disappears?

09Is it open source?

Let your agent ship it.You approve what goes live.