Pipedream today: Workflows retirement and Connect

Start with the Workflows retirement

Pipedream officially announces retirement of Workflows and String on March 31, 2027, with Workflows closed to new signups and subscriptions. Connect is unaffected. The Workflows discussion here supports migration decisions by existing users, not adoption as a new business-workflow platform.

Identify what you are buying

Distinguish an internal API job from adding integrations for customers of your own application. Customer-facing connections introduce per-user authentication and account lifecycle questions. Match the product name on the public offer to the actual workspace offer before using either to build a budget.

Keep custom code bounded

Separate standard actions from transformations that truly require code. Document example inputs, outputs, error behavior and dependencies for every custom step. A short script is still a maintained integration when an upstream field change can interrupt the business process; line count is not an operating-cost measure.

Check production eligibility explicitly

The current public Connect offer separates development from production. A successful free experiment does not establish that recurring production use is free. For existing Workflows usage, use the relevant legacy workspace terms and limits; Connect pricing is not a substitute for the retiring product’s contract.

Observe compute and upstream limits

Workflows documentation ties compute accounting to time and memory. Observe representative executions containing slow APIs, large files or loops. Also define what happens at an upstream quota: retry, queue for later, or request human review. A platform allowance cannot remove the destination service’s limits.

Preserve the integration specification

For migration, record scopes, owners and revocation procedures without copying secrets into documentation. Check what the official export tool retains, then revalidate inputs, transformations and outputs on the destination. Keep Connect settings distinct from the retiring Workflows scope when deciding what needs to move.

• Compare operation with n8n

Create a retirement migration inventory

Inventory each existing workflow’s trigger, frequency, stored outputs and connection owner. Daily execution alone does not establish priority: a billing operation and a disposable report have different consequences. For critical work, establish how inputs and outputs will be reconciled before switching.

An exported structure is not a guarantee that another product can execute it unchanged. Recreate authorized connections and verify equivalent business outcomes with representative inputs. Retire old work only after its replacement is validated, and maintain an explicit list of what has not yet moved.

Choose a replacement by maintained responsibilities

Select a replacement entitlement that supports maintained logic, connections, volume and reviewer access. Do not transfer the old meter unchanged into another product’s units. First establish equivalent inputs and outputs, then compare ordinary, concentrated and replay scenarios with labelled cost assumptions.

Move from saved structure to validated cutover

Use the official retirement and deletion timeline to secure configuration, necessary records and connection ownership. Export alone does not complete migration; verify equivalent outcomes at the destination. Separate cleanup of retiring Workflows from unaffected Connect settings or deletion of an entire account.

• Choose a destination by job type