Pipedream Connect after the Workflows shutdown

Pipedream sells two products under one name, and only one of them is closing. Workflows (the visual builder with code steps, triggers and data stores) and String (the AI workflow builder) shut down on March 31, 2027. Connect (the developer toolkit for adding integrations to your own app or AI agent) continues. If you use both, you need to know exactly where the line runs. This page draws it, using only Pipedream's own statements.

What Pipedream says

The shutdown notice puts it plainly: if you use the Connect API, MCP Servers, or API Proxy, nothing changes; Connect "remains fully supported and actively developed". On data, it says only Workflows data is deleted automatically, and Connect settings and credentials are not affected. The reason given for the shutdown is a focus on being the integration layer that connects AI to the outside world; Workflows falls outside it.

What Connect is

From the Connect overview, Connect is a toolkit for your product, used through SDKs and the REST API:

Part	What it does
Managed auth	Your end users connect their accounts (OAuth or API keys) to 3,000+ apps; Pipedream stores the credentials
Pre-built tools (actions)	Run Pipedream's registry actions on behalf of your users
Triggers	Deploy event sources for your users' accounts and receive events at your webhook URL
API Proxy	Send any request to an integrated API; Pipedream inserts the user's credentials
MCP servers	Give AI agents 10,000+ tools across 3,000+ APIs
Environments	development (up to 10 external users, any plan) and production

If your code calls @pipedream/sdk or api.pipedream.com/v1/connect/..., you're a Connect user.

The line between them

You use	After March 31, 2027
Connect managed auth for your users	Keeps working
Connect actions and the API Proxy	Keep working
Connect triggers delivering to your webhook	Keep working (Connect feature)
Pipedream MCP servers in your agent or in Claude/ChatGPT	Keep working
Workflows in the builder (HTTP, schedule, app triggers, code steps)	Stop
Workflow data: data stores, File Stores, event history, workflow connected accounts	Deleted by April 30, 2027
String	Stops
Workflows you run for end users via Connect	These are Workflows; plan for them to stop (see below)

The grey zone: workflows for end users

Connect's docs include a page on running workflows for your end users: you build a workflow in the Pipedream builder with an HTTP trigger and invoke it for a given external user. The feature uses the Workflows product. The shutdown notice names Connect API, MCP and API Proxy as unaffected and doesn't list this feature among them, while it covers Workflows as a whole. Our reading: treat these workflows as part of the shutdown and move them, unless Pipedream tells you otherwise in writing.

Connected accounts: two different stores

Accounts your team connected for use in Workflows are Workflows data: the notice says credentials and OAuth tokens of connected accounts are deleted by April 30, 2027. Accounts your end users connected through Connect managed auth are Connect credentials and are not affected. Same dashboard, different fate.

Splitting a mixed setup

A common pattern: your app uses Connect for user authentication, and a few Pipedream workflows do the processing (webhook in, call the user's Slack via their connected account, write to your database). After the shutdown the auth keeps working but the processing doesn't. Options:

1. Move the processing into your backend. Your server receives the event and calls the user's apps through Connect actions or the API Proxy. Connect stays the integration layer; you own the logic. Best when the workflows are small and your team already runs a backend.
2. Move the processing to a workflow tool such as n8n. n8n receives the event on a Webhook node and calls the user's apps either with its own app nodes and credentials, or with an HTTP Request node to the Connect API Proxy. Best when non-developers maintain the logic or there are many workflows.
3. Mix: keep user-facing integrations on Connect and move internal automations (alerts, reports, syncs for your own team) to n8n.

For internal workflows, n8n's own credentials replace Pipedream's connected accounts; there's no reason to route your team's Slack through Connect. For per-end-user integrations, Connect is still the simpler option, because n8n's per-user OAuth (end-user credentials) is an Enterprise feature, marked preview on n8n's pricing page.

Billing

Workflows subscriptions are cancelled on March 31, 2027 with a prorated refund. Connect has its own plans on pipedream.com/pricing: Free, Startup ($99/month billed annually or $150 monthly, 10,000 credits, then $0.012 each) and Business (custom), as of October 21, 2026. In development mode all Connect features are free on any plan, with up to 10 external users (environments). Details in Pipedream pricing.

Checklist

1. List everything in your Pipedream workspace: projects and workflows (Workflows), Connect projects (Connect).
2. For each workflow: internal or run for end users? Both need a new home.
3. Export every project with workflows: export Pipedream workflows.
4. Back up data stores and File Store files before March 31, 2027.
5. Leave Connect projects, OAuth clients and end-user accounts as they are.
6. Re-test your Connect integration after the Workflows parts are moved, in case something depended on a workflow URL.

Moving the Workflows side to n8n

Upload the project exports to our converter: it maps triggers and steps to n8n nodes and lists what needs manual work, including every connected-account credential you'll have to recreate. Code steps can be checked one at a time with the code step checker. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. The full process is in migrate Pipedream to n8n, and the dates are in Pipedream shutdown.

Not affiliated with Pipedream or n8n.