Pipedream

Verdict

Do not start a new Pipedream Workflows deployment. Workflows is in maintenance mode, stops running on March 31, 2027, and its data is permanently deleted by April 30. Existing users should export now, inventory the state the export omits, and migrate before the final weeks. Consider Pipedream Connect only for a different job: embedding managed authentication, actions, triggers, MCP tools, or an API proxy into a product or AI agent. Connect remains supported, but your application owns orchestration, approval, idempotency, durable state, and recovery.

For workflow buyers, the relevant split is between two products with very different jobs. The retiring Workflows product is the hosted visual and code-based automation builder commonly compared with n8n and Make. Connect is a developer toolkit for adding customer-facing integrations to an application or agent. Workday closed its acquisition of Pipedream during its fiscal 2026 fourth quarter, and Pipedream's current privacy statement identifies it as a Workday company.

Use the best AI workflow automation tools when the requirement is still a durable workflow builder. n8n is the closer option when code, visual orchestration, and self-hosting matter; Make is the managed visual alternative. Dify fits model-backed applications and RAG better than general SaaS orchestration.

Workflows and Connect are not substitutes

Pipedream's shutdown notice says Connect API, MCP Servers, and API Proxy are unaffected. That does not turn Connect into a replacement workflow runtime. Connect exposes integration building blocks; the calling application supplies the scheduler or agent loop, business state, approval path, retries, observability, and operator controls.

Decision criteria

Current Connect pricing and limits

The public pricing page was checked October 18, 2026. It prices Connect, not a new Workflows subscription.

An external user is one distinct user identifier that connects at least one account. One user with five connected apps counts once. Production is a paid boundary: development provides API, SDK, and MCP access for building and personal testing, while serving real external users requires Startup or Business.

One Connect usage credit covers each 30 seconds of compute for an action execution, MCP tool call, Connect proxy request, or event emitted from a deployed trigger to its subscribed webhook. Listing apps or accounts, configuring components, and other management calls do not consume credits. Model tokens, the upstream SaaS API, your own compute and storage, queues, logs, and review system remain separate costs.

Current Connect API limits include 100 Connect-token creations per minute per external user, 2,000 account-management requests per five minutes per project, and 3,000 component-list requests per five minutes per project. Customer-defined rate-limit tokens can add a narrower application limit. The API Proxy terminates requests after 30 seconds and returns 504; it also restricts forwarded headers and targets requests to each app's allowed domains.

Pipedream's retained Workflows pricing documentation describes a separate legacy meter: one credit per 30 seconds of compute for each workflow segment at 256 MB, with proportional increases for memory and charges for dedicated workers. That matters only to existing subscribers during migration. There is no current public Workflows offer to recommend, and the account's billing meter is the relevant source for its remaining subscription.

Exporting is only the first migration step

The official export tool creates a ZIP for one project at a time. Each exported workflow JSON captures the latest deployed version, including triggers, steps, code, configured props, settings, and control-flow branches. The manifest records skipped workflows and warnings.

The export requires File Stores and stops at 500 workflows or 256 MB per project. It excludes credentials and OAuth tokens, secret values, environment variables, event history, data stores, File Store files, and code for private multi-file components. Never-deployed workflows are skipped. Download files separately, preserve private-component source, inventory each data-store key and cursor, record webhook URLs and schedules, and reconnect every account on the destination.

Run old and new paths side by side with non-destructive or shadow outputs where possible. Cut over webhook senders and schedules deliberately, then verify counts and side effects before disabling the original. Pipedream says Workflows data, including connected-account credentials and OAuth tokens, will be deleted by April 30, 2027; do not treat the vendor deletion date as a backup plan.

Approval belongs in the host application

Connect actions are invoked on demand and can write to third-party systems immediately. Current Connect documentation describes action execution, managed credentials, MCP, and proxy calls, but does not document a Connect-owned human-review state machine. Existing Workflows could suspend and resume, but building a new approval dependency on a runtime that ends in March would be self-defeating.

For an agent, classify tools as read-only or consequential and hold the consequential call in your own durable approval record. Display the exact account, operation, recipient or object, parameters, and source evidence. Bind approval to a payload hash and expiry, then revalidate current state before invoking Connect. A model's instruction to ask first is not an authorization control.

Keep OAuth scope narrow. Pipedream-managed OAuth clients can run prebuilt tools and proxy requests, while retrieving raw user credentials or invoking workflows requires a custom OAuth client according to the current OAuth client matrix. Provider approval rules can still apply to a custom client.

Recovery is a caller responsibility

Connect action errors include best-effort attribution to component code, an upstream API, network I/O, or response parsing. The documentation labels network failures and some upstream 5xx responses as potentially retryable; 4xx, component-code, and parsing failures generally require inspection or a fix. That classification is useful input, not a complete retry policy, and Pipedream warns it can be wrong.

Existing Advanced-plan Workflows can retry a failed step up to eight times over ten hours with exponential backoff. The legacy settings documentation says out-of-memory and timeout failures are excluded. Inventory that behavior during migration: it does not automatically transfer to Connect or a replacement platform.

Persist an idempotency key before every write, record the upstream object ID on success, and reconcile after timeouts before retrying. Cap exponential backoff, honor Retry-After, and route exhausted attempts to an operator. Pipedream's webhook documentation provides HMAC-SHA256 signatures and recommends rejecting stale timestamps to reduce replay risk. Validate signatures against the raw request body, keep a processed-event ledger, and rotate the signing key without losing verification during deployment.

Do not infer delivery durability from a successful trigger deployment. The trigger-events endpoint retrieves recent events and returns at most 100 per request. That response limit does not establish a durable event archive; keep your own queue and reconciliation records. Test provider outage, receiver outage, duplicate delivery, out-of-order events, deleted accounts, expired credentials, and the ambiguous case where an upstream write succeeds but the response is lost.

Privacy is narrower for Connect payloads, not zero-data

Pipedream says it does not store or log API or MCP request payloads and response bodies for Connect. It still stores connected-account credentials and project configuration. OAuth grants, key-based credentials, and environment variables are encrypted at rest; Connect credentials are separated between development and production environments. Pipedream hosts on AWS in us-east-1 and says customer data at rest uses AWS KMS-managed encryption.

Deleting a connected account through Connect removes that account and its associated credentials. Pipedream's security documentation separately warns that deleting an OAuth grant inside Pipedream does not revoke the upstream provider's grant; revoke it at the provider too. Code and configuration are retained until deletion, event and execution logs follow account retention rules, and most internal or subprocessor logs are deleted within 30 days, with a subset kept longer for security investigations.

The privacy statement, effective February 2, 2026, says Pipedream may share personal information with Workday affiliates for support, marketing, technical operations, events, and account management. When Pipedream processes customer personal data, the DPA governs that processor relationship. Verify the signed contract, subprocessor list, retention, residency, and the third-party APIs' terms for the actual data path.

One community report captures the migration cost

On October 1, 2026, Reddit user u/mrryanthartigan linked Pipedream's shutdown and export notices, wrote that the JSON export did not make the problem easy, and asked where users should migrate. Commenters suggested n8n or Make and discussed the cost of recreating managed OAuth.

That thread is a reaction from individual users, not evidence that a particular migration target works, that every workflow is difficult to move, or that Connect is unreliable. The first-party export specification establishes the concrete migration gaps; the community report shows why at least one operator viewed those gaps as material.

We did not create or authenticate a Pipedream account, connect an app, invoke an action, deploy a trigger, inspect private dashboard limits, export a project, test approval, replay a failure, or benchmark reliability for this profile. Prices, limits, lifecycle dates, controls, and migration boundaries come from current first-party pages; the migration sentiment above is attributed to its dated community source.

Choose Pipedream Connect when managed auth and a large integration registry remove enough product work to justify building the orchestration and operating controls around it. For an existing Workflows estate, export now and migrate. For a new visual automation program, compare n8n and Make instead.

For implementation planning, see build human-approved automation flows, automate document intake and extraction, and route and summarize support tickets.

For the later stage of an exit, the Relay.app shutdown profile covers rebuilding after service access and export windows have already ended.

Sources & further reading

• Current Connect plans, prices, usage credits, users, and security features
• Connect and legacy Workflows credit definitions
• Official Workflows and String shutdown notice
• Official project export scope and limits
• Connect overview, products, and data-handling summary
• Connect development and production environments
• Connect API rate limits and customer-defined rate-limit tokens
• Connect API Proxy behavior and timeout
• Connect action execution and error attribution
• Legacy Workflows retry and retention settings
• Connect webhook signatures and replay protection
• Connect trigger event retrieval limits
• Pipedream and custom OAuth client boundaries
• Pipedream privacy, credential security, hosting, retention, and deletion
• Pipedream privacy statement effective February 2, 2026
• Workday fiscal 2026 results confirming the Pipedream acquisition closed
• Community reaction to the Workflows shutdown and migration burden