How to Build Your First Pipedream Workflow in 15 Minutes
Pipedream is a serverless workflow builder for developers: you pick a trigger, chain steps, and drop Node.js, Python or Go code inline when the 10,000-plus prebuilt actions don’t fit. It is free up to 25 credits per month, and a scheduled workflow that polls every 15 minutes will eat that budget fast.
The short answer for people in a hurry: build the workflow in the browser, use a free-tier-friendly trigger (HTTP or webhook), and keep loops inside a single code step instead of fanning out dozens of node-level steps. That last habit is what separates a workflow that costs nothing from one that costs $29/month.
What does a Pipedream workflow actually look like?
A workflow is three things: a trigger, one or more steps, and the data passed between them via steps.node_name.$return_value. Nothing is containerised, nothing gets deployed. You save it, and it runs.
Open pipedream.com, hit New Workflow, and you get an empty canvas. Every step has an editable name, which matters more than it sounds. Renaming a step to parse_invoice instead of node_2 saves you an hour of debugging when the payload shape changes.
Step 1: pick a trigger that fits the free plan
Triggers come in three families:
- App triggers — poll a source like Gmail or Airtable. Each poll costs credits.
- HTTP / Webhook triggers — nothing is polled. You get a unique URL and the workflow wakes up when data arrives.
- Schedule triggers — cron syntax. Useful, but a 15-minute interval is 2,880 runs a month, so budget carefully.
For a first build, choose HTTP. Send a single JSON object to the URL with curl -X POST and you’ll see the event appear in the trigger panel within about a second.
Step 2: add a prebuilt action
Assume you want each posted payload to become a row in Google Sheets. Search for Google Sheets → Add Single Row, connect your Google account via OAuth (Pipedream handles this, you never paste a client secret), then map fields with the autocomplete picker.
Use {{steps.trigger.event.body.email}} and the like. The double-brace syntax is a JavaScript expression evaluated at runtime, so {{steps.trigger.event.body.email.toLowerCase()}} also works.
Step 3: drop in a code step where the actions stop
Prebuilt actions cover the common case. The discounting, the de-duplication, the weird date format from a legacy system — that’s a code step.
Take the voucher and amount to Node.js (v20) and write roughly this:
const rows = steps.trigger.event.body.orders ?? [];
export default defineComponent({
async run({ steps, $ }) {
const total = rows.reduce((a, r) => a + (r.amount || 0), 0);
return { total, count: rows.length };
}
});
One code step handling 500 rows costs exactly the same as one handling one row. Fifty steps each handling 10 rows does not. That is the single most useful cost fact about Pipedream.
Is Pipedream’s free plan enough to learn on?
Mostly yes, with a caveat. The free tier gives you 25 credits per month, a 30-second execution timeout and 100 daily invocations on HTTP triggers. A learning project with a few manual runs will not touch 25 credits.
What burns credits: high-frequency app polling, $.flow.delay in long fan-out workflows, and any step that runs more than once per event. The paid tier starts at $29/month for 10,000 credits if you need serious polling.
When does the timeout bite?
The 30-second ceiling is generous for API chaining and tight for PDF parsing or large batch work. If a step needs two minutes, you want a different runtime, not a bigger plan — Pipedream is for glue, not for heavy compute.
Step 4: test before you point it at production
Click Test on each step in order. Pipedream stores the last event per step, so downstream steps always see real shapes rather than your guess at them. That single design choice removes most of the guesswork from debugging.
Once it works, hit Deploy. The URL stays stable. Keep a separate copy of the workflow as your staging version if you’ll keep editing it.
Step 5: make it observable
Add a final step that posts to Slack on failure, or wrap the risky call in try/catch and return { ok: false, error }. Pipedream’s built-in Event History keeps recent runs with full logs; older runs roll off, so export anything you need to keep.
Who should skip Pipedream
If you have no code comfort at all, Zapier’s step-by-step UI is friendlier and its 5,000+ app catalogue is broader in the long tail. If you’re orchestrating long-running jobs with retries measured in hours, a real queue or Temporal-style engine fits better. Pipedream wins in the band where you want code and no infrastructure.
Quick Summary
- Pipedream is a hosted workflow tool where steps are code-first, with 10,000+ prebuilt actions.
- Free plan: 25 credits/month, 30-second timeout per execution; paid starts at $29/month.
- HTTP and webhook triggers don’t poll, which makes them the cheapest way to prototype.
- One code step beats fifty steps: credit cost is per step execution, not per item processed.
- You need some JavaScript: the autocomplete pickers help, but real workflows end up in code.
Related guides
- Set up a hotjar survey that finds issues — the same trigger-and-inspect pattern, applied to user research.
- Install hotjar and get usable heatmaps — for reading the traffic your workflow will generate.
