Automation · checked 2026-10-19

Can I vibecode Pipedream?

KINDA· weekend project

Pipedream built its name on workflows, but those shut down on March 31, 2027; what it sells now is Connect, a hosted token vault, OAuth flow and MCP server in front of 3,000+ APIs. For one person the core is small: keep tokens for the handful of services you use, refresh them, run webhook and cron handlers, and expose a few tools to your agent. An agent builds that in a weekend. What it can't copy is the breadth: OAuth apps already registered for hundreds of providers, and 10,000 prebuilt tools that someone keeps current as those APIs change.

$150/moprice

$1,800you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyAdvanced · Real infrastructure or OAuth work.

TimeA weekend; registering the OAuth apps is the slow part

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
An OAuth app per providerGoogle's consent screen in Testing status expires refresh tokens after 7 days.
A public address for webhooksA tunnel or a small VPS with HTTPS; skip it if you only run cron jobs.

Before you buildFree is development only, so production traffic needs Startup. If all you need is webhooks and cron jobs for yourself, self-hosted n8n or Windmill covers that without a build.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a personal integration gateway to replace Pipedream for my own scripts and agents. Requirements:

- Node.js 22 + TypeScript: a Hono server on http://127.0.0.1:4880 with a small server-rendered
admin page (vanilla JS) and a JSON API. `npm start` runs everything.
- Storage: better-sqlite3 in ./data/gateway.db for connections, handlers and run logs. Access and
refresh tokens are encrypted with AES-256-GCM using GATEWAY_KEY from .env.
- Connections: OAuth 2.0 authorization code with PKCE for GitHub, Google (Gmail, Calendar, Sheets)
and Slack, using client IDs and secrets I register myself and keep in .env; plain API-key
connections for anything else. Refresh tokens 5 minutes before expiry and mark a connection
"needs reauth" when a refresh fails.
- Proxy: POST /proxy/<connection>/<path> forwards the request to the provider with a fresh token
injected. A token never appears in a response, a log line or an error message.
- Handlers: TypeScript files in ./handlers/, each exporting a trigger (webhook name or cron
expression, via `croner`) and run(event, ctx); ctx.fetch(connection, url) goes through the
proxy. Run each in a worker thread with a 30-second timeout and log input, output, duration and
errors for 30 days.
- Webhooks: POST /hooks/<name> with an HMAC signature check per handler (secret in .env), a 1 MB
body limit, and a replay button for any logged event.
- MCP: expose every handler and each connection's proxy as tools on a Streamable HTTP MCP endpoint
at /mcp (`@modelcontextprotocol/sdk`), guarded by a bearer token from .env.
- Single user. No accounts, no telemetry, local-first; outbound calls go only to providers I connect.
- Out of scope: a visual workflow editor, per-user connections for other people, and the other
3,000 apps (a provider is added by editing a config file).
- README: how to register each OAuth app (a Google consent screen left in Testing status expires
refresh tokens after 7 days), exposing webhooks with a tunnel, and backing up the database and
GATEWAY_KEY together.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Pipedream.

Add a Pipedream importer to the gateway in this folder. Requirements:

- A command `gateway import-pipedream <zip>` that reads a project_export zip: one JSON
  file per workflow plus manifest.json.
- For each workflow with status `exported`, write a TypeScript file in ./handlers/ with the
  trigger (HTTP, cron or an app event as a TODO), and one commented block per step holding
  the original step type, props and code.
- Copy Node.js code steps as functions where possible; mark app steps that need a provider
  as TODO with the app name.
- Print the manifest warnings and every skipped workflow in a summary; never overwrite a
  handler that already exists.
- Update the README with how to export a project from Pipedream.

Add a small data store to the gateway in this folder. Requirements:

- ctx.store.get, set, delete and list(prefix), backed by a SQLite table scoped per handler.
- Optional TTL in seconds per key; expired keys are removed by a nightly job.
- Values are JSON, at most 256 KB each; reject anything larger with a clear error.
- An admin page that lists keys per handler and lets me edit or delete a value.
- Update the README.

Add failure alerts to the gateway in this folder. Requirements:

- When a handler run fails or times out three times in a row, send one message to an ntfy
  topic or a Slack incoming webhook from .env, with the handler name and the last error.
- Send a recovery message when the next run succeeds; never send more than one alert per
  handler per hour.
- Show the current failure streak per handler on the admin page.
- Update the README.

Add Notion as a provider to the gateway in this folder. Requirements:

- A config entry for Notion's OAuth 2.0 flow with NOTION_CLIENT_ID and NOTION_CLIENT_SECRET
  in .env, and the Notion-Version header sent on every proxied call.
- Check Notion's docs for whether access tokens expire; if they don't, skip refresh for this
  provider and say so in a code comment.
- A sample handler that appends a row to a database on a webhook call.
- Update the README with how to create a public integration in Notion.

What you lose

Hosted OAuth for 3,000+ APIs without registering an app at each provider
10,000+ prebuilt tools and triggers that Pipedream keeps working
Managed runtime, scaling and a SOC 2 Type 2 attestation
Per-user connections: letting other people link their own accounts
A visual workflow builder, which is closing anyway

Why people still pay

Teams building agents or products that act inside their users' accounts pay so they never register OAuth apps for dozens of providers, wait on app reviews, or keep token refresh alive. They also get a catalog of tools already wired to those APIs. For one person with five accounts that is a lot to buy; for a product with hundreds of users it is the shortcut.

Moatintegrations infrastructure scale

Do the math

Pipedream or your own copy?

Over

Your usage

Count my time12h ×$/h

Pipedream, 1 yr$1,800

Your own copy, 1 yr$44running + build session

You keep$1,757pays for itself in the first month

Estimate · Runs on your machine or a $5 VPS. The build is token usage on your agent plan; each extra provider is a config entry plus an OAuth app.

Leaving Pipedream

Take your data, then cancel.

1 · Take your data out of Pipedream

1Workflows: open the project, go to Settings and click Export Workflows. Pipedream builds project_export-<project_id>.zip in the project's File Store, which needs a plan that includes File Stores.
2The zip holds one JSON file per workflow plus manifest.json, which lists each workflow as exported or skipped and carries warnings about steps that need attention.
3One export per project at a time, up to 500 workflows or 256 MB; move workflows to another project to export the rest.
4Not included: secret values, environment variables, connected account credentials, event history, data stores and File Store files. Download those separately and reconnect accounts on the new platform.

2 · Cancel Pipedream

1Workflows subscriptions end on their own on March 31, 2027, with a prorated refund and nothing to do.
2Monthly Workflows subscribers can cancel earlier in account settings; annual subscribers contact support for early cancellation and a prorated refund.
3Connect (Startup) plans: change or cancel from the workspace billing settings. A cancellation takes effect at the end of the billing period, and connected accounts and sources are switched off, newest first, until the workspace fits the Free limits.

All Workflows data, including credentials and OAuth tokens, is deleted by April 30, 2027; Connect settings and credentials are not affected.
Third-party migration guides say the pipedream.net webhook URLs stop working at the shutdown, so move every sender (Stripe, GitHub and the like) to a URL you control before March 31.
Step code in Node.js or Python usually moves to n8n's code node or to Windmill with little change; event sources have no direct equivalent on every platform.
Export each project before deleting anything: the tool covers workflow structure only.

Checked 2026-10-19 against Pipedream's docs: 1, 2, 3, 4, 5

The escape hatch

Don't feel like building it? These are already free.

n8nFreeVisual workflow builder with code steps and webhook and cron triggers. Source-available under the Sustainable Use License, free to self-host for your own use.★ 208k · active Oct 2026 · docker to self-host
WebVisit ↗WindmillOpen sourceCode-first: scripts in TypeScript, Python, Go and more become webhooks, schedules and flows. AGPL-3.0 core with proprietary enterprise parts.★ 18k · active Oct 2026 · docker to self-host
WebVisit ↗ActivepiecesOpen sourceNo-code flows built from open-source pieces, with an AI agent option. MIT-licensed apart from its enterprise folders.★ 25k · active Oct 2026 · docker to self-host
WebVisit ↗

All 6 free alternatives to Pipedream ›

The numbers

Pipedream pricing

Plan	Monthly	Annual, per month	What you get
Free	$0/workspace	$0/workspace	Everything in development: 3,000+ connectors, 10,000+ prebuilt tools and triggers, MCP servers, the Connect proxy, custom OAuth clients and unlimited team members. No production environment; external users and usage credits count in development only.
Startup	$150/workspace	$99/workspace	Production environment, 100 external users included then $2 each, 10,000 usage credits a month then $0.012 each, email support.
Business	custom	—	Everything in Startup plus volume pricing for users and usage, SSO, SCIM, HIPAA, dedicated static egress IPs, SLAs and a dedicated Slack channel.

Free tier: Development only: no production environment, and external users are not billed or served in production.
Billing: Startup is monthly or annual. Upgrades apply at once; downgrades and cancellations take effect at the end of the billing period, and connected accounts are then switched off until the workspace fits the Free limits. The older Workflows product is closed to new subscriptions and ends on March 31, 2027, with a prorated refund.
Hidden costs: Cost follows your own customers, not seats: $2 for every external user past 100 and $0.012 for every credit past 10,000. Workflows, the product many people knew Pipedream for, is in maintenance mode and no longer sold.
Source: pipedream.com

Also on the list

Zapier$29.99/mo · AutomationKINDA

n8n Cloud$26.85/mo · AutomationKINDA

Make$10.59/mo · AutomationKINDA

Questions

Pipedream, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Free has every feature, 3,000+ connectors and unlimited team members, but only in development: there is no production environment.

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Hosted OAuth for 3,000+ APIs without registering an app at each provider, 10,000+ prebuilt tools and triggers that Pipedream keeps working.

About $150 a month on the Startup plan, $1,800 a year (checked 2026-10-19).

Hosted OAuth for 3,000+ APIs without registering an app at each provider; 10,000+ prebuilt tools and triggers that Pipedream keeps working; Managed runtime, scaling and a SOC 2 Type 2 attestation; Per-user connections: letting other people link their own accounts; A visual workflow builder, which is closing anyway. If any of those matter to you, keep paying.