Pipedream Problems & Issues
Real user-reported problems, complaints, and limitations for Pipedream. Based on analysis of 12 signals.
Overall score: 35/100
Issues by Category
Workflows closed to new signups and subscriptions
Third-party sources report Workflows is in maintenance mode: no new signups, no new subscriptions and no new features. Anyone evaluating Pipedream for automation today is looking at a product with an end date.
Free plan is development only; production needs a paid plan
The current pricing page lists the Free plan as development-only: no production environment, no external users and no usage credits for production. Production starts on Startup.
Credits are billed per 30 seconds and scale with memory
One credit covers 30 seconds of compute at 256 MB; memory is billed in 256 MB steps, so a 1 GB workflow costs 4x per run. Users on the community forum report unexpected debits, such as workflows that time out still consuming credits.
Timeouts: 30s for HTTP triggers, 300s free and 750s paid maximum
Default timeouts are 30 seconds for HTTP and email triggers and 60 for cron. Slow third-party APIs or large data processing hit the Timeout error, and the ceiling is 300s on free and 750s on paid.
Out of Memory and 6 MB payload limit break data-heavy workflows
Workflows with roughly 8-10 or more steps or large files held in variables hit Out of Memory. Logs, step exports and event data are capped at 6 MB combined (Function Payload Limit Exceeded), and HTTP request bodies at 512 KB by default.
No loop step: one bad record can fail a whole run
Iteration happens inside code steps, so a single bad item can fail the entire execution, and teams build their own error routing (per Kestra's migration guide, a competitor).
Pipedream Workflows is shutting down on March 31, 2027
Pipedream's docs state that Workflows and String shut down on March 31, 2027, and third-party coverage says Workflows data, including credentials and OAuth tokens, is deleted on April 30, 2027. Pipedream Connect (API, MCP servers, proxy) is not affected. Existing workflows keep running until the shutdown date.
Connected account tokens expire or get revoked and triggers go quiet
Community threads describe Invalid Credentials and Access Token Expired errors on Gmail, Jobber and others. One report says a deployed trigger stopped sending events with no error after its account died and stayed bound to the old token after reconnecting.
Export does not include secrets, connections, data stores or event history
The official export writes a ZIP with one JSON per workflow (max 500 workflows or 256 MB). Secrets are redacted, and connected accounts, environment variables, data store contents, File Store files and event history are not exported, so they must be recreated by hand elsewhere.
Webhook URLs stop working at shutdown
Each HTTP-triggered workflow has a *.m.pipedream.net URL registered in Stripe, GitHub, Shopify or internal systems. All of those endpoints stop working on the shutdown date, so every sender must be repointed.
Free plan has community-only support; email only on Startup
Free gets community support only and Startup gets email. Dedicated Slack and priority SLAs are only on the custom-priced Business plan.
SSO, SCIM, HIPAA and static egress IPs only on Business
The pricing page lists SSO, SCIM, HIPAA and dedicated static egress IPs as Business-only, which needs an annual contract and a sales conversation.
Regret Patterns
Common reasons users regret choosing Pipedream.
Built production automations on Workflows, now forced to migrate
Teams that adopted Workflows face a rebuild on another platform before March 31, 2027.
Webhook endpoints registered in many services
Every sender pointing at a pipedream.net URL has to be repointed, and a missed one fails silently.
Credits spent on slow APIs and big memory
Long calls and high memory settings multiply credit use more than expected.
Free plan turned out to be dev only
Expecting to run small production jobs for free, then needing Startup.
Lost data not covered by export
Data stores, secrets and event history are not exported and have to be saved separately.
When Pipedream Breaks Down
Specific scenarios where Pipedream fails or underperforms.
Migration after the shutdown notice
Credentials, connections, data stores and event history are not exported and webhooks need repointing.
Workflows longer than 30 seconds
HTTP-triggered workflows hit the default timeout; you must raise the setting.
Large files or many steps
Out of Memory and the 6 MB payload limit appear.
Long-lived OAuth connections
Tokens expire or are revoked and triggers can go quiet.
Bursts above 10 requests per second
HTTP triggers return 429 above the average rate limit.