Pipedream Workflows
workflow HTTP endpoint removal
Stops workingSubscribe to Pipedream WorkflowsShare
Pipedream Workflows will shut down on March 31, 2027. Requests sent to workflow HTTP endpoints on *.m.pipedream.net will fail after that date.
What to use instead of these calls
Export the workflows with Pipedream's export tool and rebuild them on another automation platform, then point the callers at its endpoints. Pipedream offers no replacement for Workflows, so choosing another automation platform is your team's decision, though Pipedream Connect is not affected.
Pipedream offers no replacement for Workflows: choosing another automation platform is the team's call.
In Pipedream Workflows's words
We want to let you know that Pipedream Workflows and String will shut down on March 31, 2027.
Facts
- API
- Pipedream Workflows
*.m.pipedream.net - Kind
- Removal
- Takes effect
- March 31, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Pipedream Workflows's own pages
Questions
When does this change take effect?
Calls to A workflow HTTP endpoint on Pipedream Workflows stop working on March 31, 2027.
What happens to calls after March 31, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 31, 2027.