Never used Pipedream v1? You can skip this migration guide and read on about Steps.
- Edit & test your workflows in separate editing mode without impacting live workflows
- Support for multiple languages including Node.js, Python, Bash and Go
- Granular testing including the ability to test individual steps and more
- Multiple triggers are now supported per workflow
- Improved forms for easier configuration and streamlined building
- Read our quickstart, docs, and/or FAQ
- Have questions? Ask here or on Discourse
- As a reminder, all integration components are source-available and hosted on GitHub. You can contribute your own components or improve existing ones.
New Builder Overview
Fundamentally, the new version of the workflow builder gives you the same abilities to build, test and deploy your workflows. However, you’ll notice some differences in how to build workflows.Building vs Inspecting
In v1, building your workflow and inspecting past events were visible in the same view. The new v2 builder has improved this by separating the workflow Builder from the workflow events Inspector. Switch between these contexts using the menu in the top right of the workflow builder.


Testing Changes
In the v1 workflow builder, you had to deploy the whole workflow to test changes to any step. To make changes to a deployed workflow, you had to made edits on the live version. We’ve improved this flow. Now you can test your changes with a new Test button without effecting the live version of the workflow. In addition to testing single steps, you can now selectively test portions of your workflow (e.g. all steps above or below the selected step):
Testing individual events
Not only can you test portions of your workflow in isolation, but you can also select a specific event to run against your workflow. In the Test Trigger portion of your trigger, you can select a past event seen by the workflow and build your steps against it - without having to re-trigger it manually:
Deploying Changes
After you’re happy with your changes, deploy them to your production workflow. Just click the Deploy button in the top right hand corner of the screen. After deploying your changes, your workflow is now live, and any changes you made will run against incoming events.Node.js Code Step Changes
There are a few changes to the Node.js code steps that you should know about. Some functions have been renamed for more clarity, and we’ve aligned the Node.js code steps closer to the Component API.Code Scaffolding Format
In v1, the Node.js steps would automatically scaffold new Node.js steps in this format:defineComponent
function:
- The
event
from the trigger step is still available, but exposed insteps.trigger.event
instead. - The
$
variable has been passed into therun
function where your code is executed.
$
as the entry point to built in Pipedream functions. In v1, this special functions included $end
, $respond
, etc. In v2, these have been remapped to $.flow.exit
and $.respond
respectively.
These changes unify workflow development to the Component API used by pre-built actions and also allows the defining of props from within your code steps.
Using 3rd party packages
In v1, you had to define your imports of 3rd party packages within the scaffolded function:import
your packages in the top of the step, just like a normal Node.js module:
Step Exports
In v1, you could assign arbitrary properties tothis
within a Node.js step and the properties would be available as step exports:
Using
return
to export data is the same from v1 to v2. You can still return
data, and it will be available to other steps with `steps.[stepName].$return_value.Exiting a workflow early
In v1, the$end
function can be called to exit a flow early:
$.flow.exit
:
Params vs Props
In the v1 builder, you could pass input to steps usingparams
. In the v2 builder, you pass input using props.
You can still enter free text and select data from other steps in pre-built actions. Also can add your own custom props that accept input like strings, numbers and more just like in v1.
Defining params
In the v1 workflow builder, params could be structured or unstructured. The params schema builder allowed you to add your own custom params to steps. In v2, you can add your own custom props without leaving the code editor.
Connecting apps
In the v2 builder, you can connect apps with your code using props. Above therun
function, define an app prop that your Node.js step integrates with:

HTTP Response
You can still return an HTTP response from an HTTP-triggered workflow. Use$.respond
to send a JSON or string response from the HTTP call that triggered the workflow.

Known Gaps & Limitations
However, some features from the original builder are not currently available in v2. The Pipedream team is working to quickly address these items, but if you have feedback that isn’t listed here, please reach out.Sharing workflows
At this time, sharing is not yet implemented in v2 of the workflow builder. As workaround, create your workflows in a organization which make workflows available to your team members. If you need assistance transferring workflows across accounts, please contact us.$checkpoint
The $checkpoint
functionality to save data between workflow runs is not supported in v2, and has been replaced by Data Stores.
Public workflows
At this time, all v2 workflows are private. Unfortunately at this time there is no workaround. We’ll announce when a workaround for this limitation is available. If you’re working with Pipedream support to troubleshoot your workflow, you can share it with the support team under your workflow’s Settings.Rolling back a specific version
In v2, you can test and save your progress on a workflow without deploying it. However, after deploying it’s not possible to rollback to a prior version of a deployed workflow. You can still edit a deployed workflow, just like in v1 but automatic version rollbacks are not currently possible.Replaying production events
In the v2 builder, you can still view individual events that trigger your v2 workflows in the Inspector events log. You can delete specific events or all of them in one click as well. To replay past events against your deploy v2 workflows, open the event’s menu and click Replay Event. This will rerun your workflow with this same event.FAQ
What are the benefits of the new (v2) workflow builder?
- Edit & test your workflows in separate editing mode without impacting live workflows
- Support for multiple languages including Node, Python, Golang & bash
- Granular testing including the ability to test individual steps and more
- Multiple triggers are now supported per workflow
- Improved forms for easier configuration and streamlined building
What are the limitations of the new (v2) workflow builder?
$checkpoint
has been removed from v2 workflows, but Data Stores provides a similar API.- Sharing workflows is not supported
- Making workflows public is not supported