Tool Intelligence Profile

Pipedream

Code-first serverless automation: Node/Python/Go/Bash, 3,000+ apps, credit-based compute. Free tier; paid from ~$29/mo. Connect/MCP for embedded integrations. Workday-owned.

Automation freemium 0

Pricing

Contact Sales

freemium

Category

Automation

6 features tracked

Feature Overview

Feature Status
data stores
event sources
1000 integrations
workflow automation
custom api endpoints
serverless execution

Overview

Pipedream is a developer-first, serverless workflow and integration platform. You trigger workflows from HTTP webhooks, schedules, email, or app event sources; chain pre-built actions for 3,000+ apps with custom Node.js, Python, Go, or Bash code steps; and run everything on managed workers without provisioning infrastructure. The company (San Francisco) also ships Pipedream Connect—SDKs and managed auth so product teams can embed the same integrations and MCP tools into their own apps and AI agents.

Billing is hybrid: a plan platform fee plus credits that track compute time and memory (not per step or per “task”). Public registry event sources that trigger a workflow do not consume credits; testing in the builder is free. There is no self-hosted product—everything runs in Pipedream’s cloud (primarily AWS us-east-1).

In November 2025 Workday announced a definitive agreement to acquire Pipedream as an integration platform for AI agents (3,000+ connectors). The public product and self-serve pricing remained live afterward, with homepage messaging that Pipedream has joined Workday. Treat enterprise packaging and long-term roadmap as Workday-influenced; re-check terms if you are a competitor in HR/finance stacks.

Quick take: Pick Pipedream when you want Lambda-like code control plus managed OAuth and a huge action catalog. Prefer Zapier/Make for non-technical builders, n8n when you must self-host, and a pure embedded-auth vendor if Connect branding/observability is not enough. Free is real for light prototypes; production usually means Basic/Advanced plus credit headroom—or Connect if end users auth through your product.

Key features

  • Code-first workflows — Ordered steps: pre-built actions and/or full code (Node.js, Python, Go, Bash). npm/PyPI access; step exports pass data downstream. Not a bolted-on “Code by Zapier” corner case—the platform assumes you will write code when connectors fall short.
  • Triggers & event sources — HTTP (unique webhook URL), cron/schedule, email inbox, and app sources (e.g. new row, new message). Custom sources can be deployed; public registry sources attached to workflows do not bill credits for the source run itself.
  • ~3,000 integrated apps / 10k+ tools — Managed OAuth and key-based connected accounts; open component library on GitHub (PipedreamHQ/pipedream). Marketplace claims evolve—verify the apps you need before migrating production.
  • Control flow — If/else, switch, filter, parallel, delay, end workflow. Branching and loops also live naturally inside code steps.
  • Data stores, file stores, destinations — Built-in KV data stores for cross-run state; destinations for email, HTTP, S3, emit, SSE; optional DB connectors (Postgres, MySQL, etc.).
  • Compute controls — Default 256MB memory (up to 10GB); default timeouts 30s (HTTP/email) / 60s (cron), max 300s free / 750s paid. Concurrency/throttling settings; optional dedicated workers to reduce cold starts (credits apply).
  • GitHub Sync & CLI — Version workflows with Git on higher tiers; CLI for deploy/ops. Projects as the unit of organization.
  • Pipedream Connect — Server SDKs (TypeScript, Python, Java), REST API, Connect Link, managed auth for your end users, API proxy, and multi-tenant tool execution—aimed at “add Salesforce/Slack/etc. inside my product.”
  • MCP servers — Hosted Model Context Protocol servers exposing the catalog (~10,000+ tools) to agents (Claude, ChatGPT, Cursor, custom). End-user MCP at mcp.pipedream.com; developer MCP via Connect. Open-source MCP Chat reference agent on GitHub.
  • Security & compliance — SOC 2 Type II (report on request), GDPR DPA with SCCs, HIPAA BAA available for customers handling PHI, encryption at rest (AWS KMS), isolated execution environments (Firecracker-style VMs), optional workspace VPCs with static egress IPs. SSO (SAML) on business/enterprise tiers.

Pricing

Figures below combine official docs (credit definition, free-plan limits, Connect end-user billing) with public rate cards reported by independent pricing analyses and competitor write-ups verified through mid-2026. The marketing pricing page is a client-rendered SPA—always confirm current numbers at pipedream.com/pricing before buying.

Plan Typical list price Included credits Highlights
Free $0 ~100 credits (hard cap; no overage) 3 active workflows; limited connected accounts; community support; max 300s execution; testing budget separate (docs: 750s test runtime/day on Free); 7-day-class event history
Basic ~$29/mo annual (~$45 monthly in third-party snapshots) 2,000 credits/mo Entry paid; ~10 active workflows / ~5 connected accounts (common public matrix); 750s max execution; email support; soft credit limit (overages bill)
Advanced ~$49/mo annual (~$74 monthly) 2,000 credits/mo (same pool as Basic in many matrices) Unlimited workflows & connected accounts; GitHub Sync; control-flow / concurrency features; longer history; higher AI token bundle
Connect ~$99/mo annual (~$150 monthly) 10,000 credits/mo Production Connect; managed auth for 100 external users; ~$2 per additional external user; MCP/tool execution for your product
Business / Enterprise Contact sales Custom SSO/SAML, VPCs, HIPAA BAA, volume pricing, SLAs, invoicing, success engineering

How credits work (official definition)

Pipedream charges one credit per 30 seconds of compute at 256MB memory (default) per workflow segment. Doubling memory roughly doubles credits for the same wall time (512MB → 2×; 1GB → 4×). A 1-second or 29-second run at default memory is still 1 credit. Delays and branches can create additional segments. Step count does not multiply credits—unlike Zapier tasks or Make operations. Development/test runs in the builder do not consume production credits. Unused included credits do not roll over (official FAQ).

Connect billing extra

Connect prices on (1) credits for action executions, MCP tool calls, deployed trigger emits to webhooks, and proxy requests, and (2) unique external end users who connect accounts. Listing/config operations generally do not consume credits. Production Connect is a paid-tier concern; development mode is free to explore.

Predictability caveat: Public pages emphasize included credits and “no hard usage limit” on paid plans, but per-credit overage rates are not always published as a simple rate card. Set a usage cap in billing settings if you need a hard stop. Fast polling (e.g. every 15 seconds) historically blew through quotas—prefer webhooks or slower intervals.

Limits & gotchas

  • Free hard stop — Free workspaces stop when daily/period free credits are exhausted; paid plans continue with overage unless you set a cap. Free also limits active workflows and connected accounts.
  • Execution time ceiling — 300 seconds (5 min) free; 750 seconds (12.5 min) on standard paid tiers. Long backfills need chunking or external workers.
  • HTTP QPS — ~10 requests/second average per endpoint (bursts tolerated); 429 when exceeded. Paid customers can request higher limits.
  • Payload size — Default HTTP body ~512KB; larger payloads need upload-body modes (up to multi-TB interfaces with other constraints). Combined logs/step exports/event observability capped around 6MB per execution.
  • Cold starts — Workers are ephemeral (~minutes idle). Interactive UX (slash commands, user-facing APIs) feels laggy until dedicated workers are enabled (costs credits; warm-up not instant).
  • No self-host — Cloud only. Data residency is primarily US AWS; EU-only residency is not a standard self-serve story—confirm with sales for regulated EU deals.
  • Connect branding — Auth flows may surface Pipedream branding; not a fully invisible white-label stack out of the box. Competitors (Paragon, Nango, Merge-style unified APIs) position here.
  • Credit math surprises — Memory bumps, retries, long LLM calls, and private custom sources (not free like public registry sources) raise burn. Community threads document free-tier credit reductions over time—do not hardcode old “25/day” marketing into capacity planning.
  • Workday ownership — Acquisition closed per company communications after the Nov 2025 agreement. Self-serve still works; multi-year roadmap and packaging may tilt toward Workday agent/enterprise use cases.

Community sentiment

Praise: Developers like writing real code with managed auth, HTTP endpoints that feel like mini backends, and compute-based economics that make multi-step glue cheap when runs are short. Connect and MCP are frequently cited as the modern reason to adopt Pipedream for AI agents and embedded product integrations. G2-style review sites emphasize ease of connecting APIs once you are past the learning curve. HN history (2019 launch through Connect and acquisition threads) treats Pipedream as a serious Zapier/Lambda middle ground.

Criticism: Non-developers bounce off the code-first UI. Credit-based cost is harder to forecast than task/operation counters—Zapier’s own pricing blog leans on that point. Free-tier credit cuts and opaque overage math generate forum frustration. Cold starts and the 12.5-minute ceiling show up as production gotchas. Self-host seekers on Reddit are directed elsewhere (n8n, Activepieces, etc.). Post-acquisition, some teams evaluate non-Workday alternatives for multi-year independence.

Community pattern: “Prototype free with code steps and webhooks; pay Basic/Advanced when workflows and accounts grow; buy Connect when your customers must OAuth inside your app—and watch polling frequency like a hawk.”

Who should use it

  • Engineers and technical PMs comfortable with JS/Python who need custom API logic, not only pre-built zaps.
  • SaaS / AI agent teams embedding multi-app auth and tools via Connect or MCP instead of building OAuth for every connector.
  • Webhook-heavy ops (Stripe events, form endpoints, internal HTTP micro-automations) that benefit from free testing and per-compute billing.
  • Not ideal for pure no-code marketers, teams that require self-host or strict EU-only residency as a default, or orgs that need invisible white-label auth without sales help.

Alternatives

  • Zapier — Broadest no-code app catalog; task-based pricing; simpler for business users.
  • Make — Visual scenario canvas; operations-based pricing; strong for complex no-code graphs.
  • n8n — Fair-code + self-host path; execution-based cloud; closer “technical” peer with data-control upside.
  • Tray.io — Enterprise iPaaS, sales-led, heavier governance.
  • Workato — Enterprise automation with recipe model and deep IT governance.
  • Retool — Internal apps first; workflows secondary when UI + data is the center of gravity.
  • Composio / Nango / Merge / Paragon — When the job is primarily embedded auth or unified APIs for your product, not general internal automation.
  • AWS Lambda + queues — Full control and cost tuning when you outgrow any iPaaS abstraction.

Verdict

Pipedream remains one of the strongest code-first automation and embedded-integration options in 2026: real multi-language code steps, managed OAuth at catalog scale, credit pricing that rewards short efficient runs, and a Connect/MCP story aimed at AI agents and multi-tenant products. Official economics center on 1 credit ≈ 30s @ 256MB, a usable Free tier with hard caps, and paid plans commonly cited around $29 / $49 / $99 monthly (annual) for Basic / Advanced / Connect, with Business custom.

Choose it when developers own automation and you value shipping glue (or agent tools) without standing up infra. Skip it when self-host, pure no-code, or fully white-label embed is non-negotiable. Because Workday now owns the company, re-validate pricing, DPA, and roadmap annually—and always re-open pipedream.com/pricing for the live slider before you commit capacity.

Head-to-Head

Compare Pipedream Side-by-Side