Skip to main content
Workflows make it easy to integrate your apps, data, and APIs - all with no servers or infrastructure to manage. They’re sequences of steps triggered by an event, like an HTTP request, or new rows in a Google sheet. You can use pre-built actions or custom Node.js, Python, Golang, or Bash code in workflows and connect to any of our integrated apps. Read our quickstart or watch our videos on Pipedream University to learn more.

​
Steps

Steps are the building blocks you use to create workflows.
  • Use triggers, code, and pre-built actions
  • Steps are run linearly, in the order they appear in your workflow
  • You can pass data between steps using the steps object
  • Observe the logs, errors, timing, and other execution details for every step

​
Triggers

Every workflow begins with a trigger step. Trigger steps initiate the execution of a workflow; i.e., workflows execute on each trigger event. For example, you can create an HTTP trigger to accept HTTP requests. We give you a unique URL where you can send HTTP requests, and your workflow is executed on each request. You can add multiple triggers to a workflow, allowing you to run it on distinct events.

​
Code, Actions

Actions and code steps drive the logic of your workflow. Anytime your workflow runs, Pipedream executes each step of your workflow in order. Actions are prebuilt code steps that let you connect to hundreds of APIs without writing code. When you need more control than the default actions provide, code steps let you write any custom Node.js code. Code and action steps cannot precede triggers, since they’ll have no data to operate on. Once you save a workflow, we deploy it to our servers. Each event triggers the workflow code, whether you have the workflow open in your browser, or not.

​
Step Names

Steps have names, which appear at the top of the step: