Pipedream alternative
Move your Pipedream workflows to ClickRuntime
Pipedream Workflows
- NowMaintenance mode. No new signups, subscriptions or features.
- Mar 31, 2027Workflows stop running. Webhook URLs stop answering.
- Apr 30, 2027Workflow data, credentials and OAuth tokens are deleted.
Source: Pipedream's shutdown notice
Why ClickRuntime
Code-first automations, like you're used to
Still code, without the plumbing
Like Pipedream, every automation is real code. Loops, branches, parsing and several APIs in one run are ordinary Python.
Built from the assistant you already use
Ask in ChatGPT, Claude, Cursor or any MCP client. It already knows your context, writes the script, tests it and fixes it.
Any app with an API
No connector catalogue to wait for. If the app has an API or sends webhooks, a script can use it.
State and versions built in
Each automation keeps its own state between runs. Every change is a new version, and a deploy that fails never replaces the working one.
Priced per run
A run is the whole automation, not compute time or steps. Unlimited users on every plan.
AI included
Scripts can classify, summarise and extract with a built-in AI model, no API key needed, including on the free plan.
Migration
Five steps per project
Export your workflows from Pipedream
Pipedream's export tool downloads the structure of your workflows as JSON, one project at a time. Do it now: everything is deleted after April 30, 2027.
Give the export to your assistant
Connect ClickRuntime to ChatGPT, Claude or Cursor, attach the JSON and ask it to rebuild the workflows. Each one becomes a draft automation you can read before anything runs.
Add your keys again
Pipedream can't export credentials. Save each API key as a secret in the ClickRuntime dashboard, or sign in through the app's OAuth. Keys never go into the chat.
Test with a real event
Your assistant turns each automation on, sends a test event or runs it once, and fixes it until the run succeeds. Run both side by side for a few days if you like.
Point your webhooks at the new trigger links
In Stripe, GitHub, Shopify or wherever events come from, replace the Pipedream URL with the automation's trigger link. Then turn the Pipedream workflow off.
These are my Pipedream workflows. Rebuild them on ClickRuntime.
Side by side
Where each Pipedream piece goes
| In Pipedream | In ClickRuntime | |
|---|---|---|
| HTTP / webhook trigger | Trigger link, with signature checks for Stripe, GitHub, Shopify, Typeform, Standard Webhooks and HMAC | |
| Schedule trigger | Schedule in plain words, in your timezone | |
| App event sources | A scheduled check that acts only on new items. Checks that find nothing aren't counted | |
| Node.js and Python code steps | One Python script per automation. Your assistant rewrites Node.js logic in Python | |
| Pre-built actions | Direct calls to the app's API. Any app with an API works | |
| Connected accounts | The app's API key saved as a secret, or the app's own OAuth sign-in | |
| Environment variables | Secrets, saved in the ClickRuntime dashboard and masked in logs | |
| Data stores | State built into every automation, plus counters by minute, hour, day, week or month | |
| $.flow.exit and filters | Ordinary if statements, loops and functions | |
| npm and PyPI packages | Pinned PyPI packages declared with the script | |
| Event inspector | Run log with output and errors, secrets masked, and replay for incoming events |
Your code
Same logic, fewer moving parts
A Pipedream workflow is a chain of steps passing data along. In ClickRuntime the whole workflow is one script, so data stays in ordinary variables and exiting early is a plain return.
Your assistant does the rewrite, including Node.js to Python. You can read every version in the ClickRuntime dashboard and ask for changes in chat.
export default defineComponent({
async run({ steps, $ }) {
const order = steps.trigger.event.body
if (order.total < 500) return $.flow.exit()
await $.send.http({ ... })
},
})from clickruntime import on_event, http
@on_event
def handle(event):
order = event.json
if order["total"] < 500:
return
http.post(...)- Signature
- Checked (Stripe)
- Events
- payment_intent.succeeded
Webhooks
One URL to change per sender
Pipedream's endpoint URLs stop working at shutdown. Each ClickRuntime automation has its own trigger link. Paste it where the old URL was, and it can check the sender's signature so only genuine events start a run.
Events that arrive are stored with the run, so you can look at what came in and replay it after a fix.
Pricing
Paid by the run, with unlimited users
Pipedream bills compute time. ClickRuntime counts runs: one execution of an automation, however long its code is. Scheduled checks that find nothing new aren't counted.
The free plan runs in production with 250 runs a month. Paid plans start at $9 a month for 2,000 runs. See pricing
Per month, for about 10,000 short runs
A Pipedream credit is 30 seconds of compute, so a short workflow uses about one per run. A ClickRuntime run is one whole execution, however many steps it has.
Migration help
Send us your export. We'll help you move it.
Email it with a line about what each one does. A person reads it, tells you how it maps to ClickRuntime, and helps until your automations are running. Leave out API keys and other secrets.
Moving from Pipedream
When does Pipedream Workflows shut down?
Can I import my Pipedream workflows?
My code steps are in Node.js. Does that matter?
Will my Pipedream webhook URLs keep working?
What happens to my connected accounts?
How is usage counted?
Will you help me move?
Keep exploring