Coming from Pipedream?
Pipedream Workflows is in maintenance mode: its official notice says shutdown is March 31, 2027, with no new signups or subscriptions; Connect is unaffected. Existing users should plan a migration around triggers, code and connected services. Whenever can rewrite a bounded business procedure from your description, with summaries and test results for review; code inspection is optional.
What you get on Whenever
You describe, AI writes it
Describe the job and review the rules and sample results. AI writes the procedure with managed connections. Pipedream String also supports AI-assisted authoring; compare migration needs and the resulting workflow rather than claiming this is exclusive.
One run, not time and memory
Whenever counts workflow executions rather than compute-time credits. Runtime limits, optional model usage and external API charges still matter; this is not a promise that every workload costs less.
One procedure, one language
Whenever writes the procedure as TypeScript you can inspect and export. Pipedream supports a choice of code languages and GitHub-synced workflow YAML; multiple languages are optional. Choose the representation and migration path that fit the job.
A concrete decision
Illustrative scenarios, not customer results or recorded runs.
Greg: no “done” without the invoice receipt
Illustrative decision, not a recorded customer run: Greg wants each paid order checked against Stripe, then an invoice created, its ID saved, and only then a confirmation sent. He specifies that an invoice failure must stop the confirmation, and an already-handled order must not be charged or invoiced again. He checks the summary, sample records, provider receipts and run history—not source code. Test a missing payment, a failed invoice and a duplicate event before publishing. Whenever fits when those prescribed steps matter more than an agent deciding them again; a fixed workflow elsewhere can fit too. No screenshot here claims these actions were actually delivered.
Jaunius: make the edge cases explicit
Illustrative decision, not a benchmark: Jaunius needs all pages of 5,000 contacts, a saved last-seen ID, updates only for changed records and a clear record of which writes failed. He brings the old workflow and sample inputs, reconnects accounts, and tests pagination, an API failure and a repeated event before switching triggers. Choose a single procedure if it makes this logic easier to maintain; the other tools can also support complex logic. An optional model that classifies a note can vary and adds runtime AI usage. Compare the monthly subscription and actual usage, not the number of steps alone.
Plan a Workflows migration, not a new signup.
Pipedream Workflows is in maintenance mode; Workflows and String shut down March 31, 2027, while Connect is unaffected. Preserve workflow rules and code, then reconnect accounts: credentials and OAuth tokens are not exported. AI authoring alone is not unique to Whenever.
Pipedream Workflows
Compute-time credits
Duration and memory, per workflow segment
Workflows credits scale with execution time and memory. This is not Pipedream Connect pricing.
Pipedream documents one credit per 30 seconds of compute time at 256 MB for each workflow segment, scaling with memory, and charges credits for dedicated workers. In its examples, a run split by a delay or a branch uses 2 credits where a 15-second linear run uses 1. Development and test runs do not use credits. Step count alone is not a cost estimate.
A run is one execution of one workflow, start to finish. AI building and editing are free within weekly usage limits; runs are metered separately.
A closer look
What changes when you describe the job in plain language and code runs it: to build, to run, and to keep.
Repeatable execution logic
Pipedream Workflows
Prebuilt actions and code steps execute the workflow you define. No model is required to select each step. Changing external data and explicit model calls can affect results, just as in other code-based systems.
Whenever
AI writes it, then published code runs the same execution logic. With identical inputs and dependencies, non-AI logic is deterministic. Changing API data, time, randomness or an optional model step can change results; this is not an exactly-once delivery guarantee.
Runs per dollar
Pipedream Workflows
Workflows are billed by compute credits, based on time and memory per segment, not one charge per action step. A lightweight multi-step workflow and a memory-heavy job can have very different costs.
Whenever
Pro includes 10,000 runs per month; see the pricing page for current US dollar prices. AI building and editing are free within weekly usage limits. Published runs are metered separately: the meter counts the whole run, not individual steps. External services and optional model calls can have their own charges.
What you can express
Pipedream Workflows
Prebuilt integrations plus Node.js, Python, Go and Bash offer a strong developer environment. Scheduler, HTTP, app, email and RSS triggers cover a broad set of integration jobs.
Whenever
Describe the business rules and review the generated workflow summary and outputs; code is available for deeper inspection. Pipedream String also offers AI authoring, so that capability alone is not a unique distinction, and its announced shutdown should guide migration timing.
Export and portability
Pipedream Workflows
Bidirectional GitHub Sync supports repository history, local edits, branches and pull requests. Exported custom code and Pipedream’s workflow orchestration are different portability questions; Git support is real.
Whenever
The TypeScript is yours: read it, edit it, export it, take it with you. Moving it to another runtime can require adapting managed connections, triggers and runtime-specific integrations.
Debugging a failed run
Pipedream Workflows
Step-level logs, errors and timing help developers inspect execution. This is a substantive debugging environment, not just a model’s summary of what happened.
Whenever
Read the generated procedure alongside its execution log and test with representative inputs. The comparison is which artifact you prefer to maintain, not whether only one tool has debugging.
Where the AI cost lands
Pipedream Workflows
A workflow can run without AI, and Pipedream credits measure the compute time a workflow uses.
Whenever
AI writes the workflow once, with free building subject to weekly AI usage limits. A published procedure runs its steps without a model choosing them. Any model call you explicitly include still runs and has its own cost.
When to keep Pipedream
Pipedream Workflows
Existing Workflows users should plan for the announced March 31, 2027 shutdown. The notice says data will be deleted by April 30, 2027. Pipedream Connect is separate and unaffected.
Whenever
Consider Whenever when AI-assisted TypeScript authoring and a workflow-run allowance match how you want to build and budget. Do not migrate expecting a proven speed or cost advantage without measuring your own workload.
Sources and scope
Official sources captured on the date shown below. These describe published features and billing rules, not independent performance tests. Check the linked documentation for current modes, plans and limits. No competitor dollar price is asserted.
Checked
Start with a workflow brief
Pick a starting point, connect your accounts and review what Whenever builds before publishing.
Build this workflowAnnounce closed-won deals in SlackCelebrates each won deal in Slack with the numbers and a short recap of how it was won.
Build this workflowPublish Instagram posts from a calendarPublishes due rows from your Instagram calendar on the cadence you choose and writes each post link back.
Build this workflowLog survey responses and alert on low scoresAdds each survey response to Google Sheets within minutes and emails the owner when the score falls below your threshold.
Build this workflowTrack keyword rankings in a sheet each weekChecks the search position of every keyword on your list, appends the history to a sheet and reports the moves.
Build this workflowRoute large expense claims to a managerLogs every expense submission in a sheet and alerts a manager in Slack when the amount is over the approval limit.Build this workflowStart with one Pipedream workflow.
Bring one bounded API workflow, describe it once, and compare what comes back with your current workflow.
Inventory code and runtime dependencies
Use your workflow or GitHub-synced files to list the trigger, step exports, connected accounts, memory needs and any delays or branches.
Translate the orchestration
Reuse the business rules, but adapt Pipedream-specific helpers and authentication. Python, Go or Bash steps may need a TypeScript rewrite or a separate service; do not assume source export means drop-in execution.
Exercise the complete request
Test sample events, response shape, errors and safe external writes. Check time and memory requirements, then disable the old trigger when the replacement is ready.