If you're building a product that connects to your users' apps, you've probably run into the same problem: every integration is its own little project. You need to manage OAuth flows, token refresh, API quirks, and all the maintenance in between. Multiply that by dozens of apps, and your roadmap disappears.
That's the problem Pipedream Connect is built to solve. But when you embed integrations in your product, you're not just choosing a tool—you're choosing a cost structure that grows with your user base. Pipedream charges for external users and for compute, and it can add up in ways that aren't obvious on the pricing page.
So before you commit, here's how Pipedream Connect pricing works, who it makes sense for, and how it compares to Zapier's options for embedding automation in your product.
A quick note if you came looking for Pipedream's workflow plans: Pipedream is shutting down its Workflows product on March 31, 2027, and it's no longer accepting new signups or subscriptions for it. Pipedream Connect isn't affected, and it's now the company's focus. That's what this article covers.
Table of contents:
What is Pipedream Connect?
Pipedream Connect is a developer toolkit for adding integrations to your own app or AI agent. Instead of building and maintaining each integration yourself, you use Pipedream's SDK, API, and hosted components to handle the hard parts.
In practice, that means:
Managed authentication: Pipedream handles authorization (or accepts API keys) on behalf of your users, for any of its 3,000+ APIs. You can use Pipedream's approved OAuth clients or bring your own.
Prebuilt tools and triggers: You get access to 10,000+ prebuilt tools and triggers, which you can add to your SaaS app or workflow builder.
An MCP server for AI agents: Pipedream's MCP server gives your agent access to those same tools, so it can take action in your users' accounts.
A proxy for custom requests: If a prebuilt tool doesn't cover your use case, the Connect proxy lets you send custom API requests without handling your customers' credentials yourself.
The tradeoff, of course, is that you're still writing code. Pipedream gives you control over how integrations work inside your product, but it expects you to be a developer who's comfortable with SDKs and APIs. Your users never see Pipedream's builder—you build the experience, and Pipedream runs the plumbing behind it.
Pipedream pricing overview
Pipedream Connect's pricing is built around two things: external users and credits. Here's how each works.
External users. An external user is each distinct person using your app who connects at least one account through Connect, identified by the external user ID you pass. One user who connects five apps still counts once. After the users included in your plan, each additional user costs $2 per month on the Startup plan.
Usage credits. Credits measure how much you use the Connect API. Running an action, calling a tool through MCP, sending a request through the Connect proxy, and emitting an event from a deployed trigger each use 1 credit per 30 seconds of compute. Management calls—like listing apps and accounts or configuring components—don't use credits. Once you're past the credits included in your plan, each additional credit on Startup costs $0.012, and that rate drops at higher volumes.
So you're paying for two different things at once: how many people use your integrations, and how much those integrations run. Either can grow without the other.
Pipedream pricing tiers
Here's how the plans break down:
Plan | Price | External users | Usage credits | Key features |
|---|---|---|---|---|
Free | $0 | Development only | Development only | Full access to build and test, 3,000+ connectors, MCP servers, unlimited team members, community support |
Startup | $99/month billed annually, or $150/month billed monthly | 100 included, then $2 per user | 10,000 included, then $0.012 per credit | Production environment, email support |
Business | Custom (annual contract) | Volume pricing | Volume pricing | SSO, SCIM, HIPAA, dedicated static egress IPs, SLAs, dedicated Slack support |
The Free plan gives you the full feature set in development, but it's for building and testing only. The moment you serve real users in production, you need the Startup or Business plan.
Here's a quick example. Say your app has 500 external users and runs about 20,000 credits' worth of actions a month:
Startup plan: $99/month (billed annually)
400 users over the 100 included: 400 Ă— $2 = $800
10,000 credits over the 10,000 included: 10,000 Ă— $0.012 = $120
Total: about $1,019/month (about $1,070 if you pay for Startup monthly)
At that scale, Pipedream suggests talking to them about volume pricing—and you'll probably want to.
Pricing per user is easy to forecast if your user count is steady. If you're growing quickly—or if you're offering Connect to every free user in your product—it scales in lockstep with your signups, whether or not those users ever run anything valuable.
Credits add a second variable. A small change in how often your integrations run, or how long each action takes, changes your bill. You'll need to think about both numbers when you build your pricing model, not just the one on the pricing page.
On the plus side, you only pay for what's actually in production. Development is free, so you can build, test, and show a working prototype before you spend anything.
Who is Pipedream best for?
Pipedream Connect makes the most sense if you're a developer or product team that wants full code-level control over how integrations work in your app, and you're comfortable building the user-facing experience yourself. It's a strong fit for AI products that need to act in users' accounts, in-app messaging to Slack or Microsoft Teams, and syncs with CRMs and spreadsheets.
It's probably not the best fit if you want something you can launch without engineering time, you're a no-code team, or you can't predict how many users you'll have and want a cost that doesn't change with every signup. In those cases, you'll want to look at your other options.
Pipedream vs. Zapier pricing
Zapier has two ways to embed automation in your product: Powered by Zapier and Zapier White Label. Both are built for the same job as Pipedream Connect, but they're priced differently, and the biggest difference is who pays and how.
Powered by Zapier lets you embed Zapier's workflow tools in your product and sponsor your users' automation. Your users still need a Zapier account (signing up is free), but you cover the task usage on their behalf, so they don't need to pay for a Zapier plan. With quick account creation, Zapier can create an account for them in the background, so they never have to visit Zapier.com or fill out a signup form. You're only billed for automation usage triggered through your embed.
Zapier White Label goes a step further. Your users connect their apps and run automations without leaving your UI, creating a Zapier account, or receiving a bill from Zapier. You're billed per task executed, and you decide how to price and package it for your customers. You can embed triggers, actions, full workflows, or AI agent connections via Zapier MCP or the Zapier SDK, and it works across Zapier's 10,000+ apps. The hosted Connect UI can be customized to match your design.
Here's how the three compare:
Pipedream Connect | Powered by Zapier | Zapier White Label | |
|---|---|---|---|
What you charge for | External users plus compute credits | Tasks used through your embed (sponsored) | Tasks executed |
Who pays | You | You (sponsor), for users enrolled | You; your users are never billed by Zapier |
Do users need an account? | Users connect accounts inside your app | Yes—a free Zapier account (can be created automatically) | No |
App coverage | 3,000+ APIs | 10,000+ apps | 10,000+ apps |
Public pricing | Yes | Not published | Not published |
How to start | Self-serve; free in development | Request form; enabled by Zapier | Limited access; contact whitelabel@zapier.com |
So what's the real difference? With Pipedream Connect, your bill has two moving parts—users and compute—and you'll want a model for both. With Zapier's approach, you're billed on tasks, which is a number you can estimate from how often you expect automations to run. If you know how many times something will happen, you can work out what it costs.
Zapier also covers much more ground: 10,000+ apps versus Pipedream's 3,000+, which matters when your customers ask for that one tool you hadn't planned for. And because Zapier maintains the OAuth client registrations across all supported apps, you don't have to.
One more thing worth knowing: with White Label, the consent screens apps like Google and Slack show will say Zapier is requesting access, because those screens belong to the third-party app. Pipedream lets you bring your own OAuth clients on every plan, which is an advantage if having your own brand on the consent screen is a hard requirement.
If you'd rather spend your energy on your product than on modeling user counts and compute time, Zapier is the better fit—especially if you want broad app coverage without building each integration yourself.
Related reading:
This article was originally published in July 2026. The most recent update was in November 2026.









