Skip to content

Commit dc7990f

Browse files
Connect pricing
1 parent 58434f8 commit dc7990f

File tree

6 files changed

+45
-68
lines changed

6 files changed

+45
-68
lines changed

docs-v2/pages/_meta.tsx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@ export default {
77
title: "Connect",
88
},
99
"connect": {
10-
title: "Overview",
10+
title: "Integrate APIs",
1111
// display: "children",
1212
},
1313
"--workflows": {
1414
type: "separator",
1515
title: "Workflows",
1616
},
1717
"workflows": {
18-
title: "Workflows",
18+
title: "Build Workflows",
1919
// display: "children",
2020
},
2121
"--platform": {

docs-v2/pages/connect/api-proxy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ import { createBackendClient } from "@pipedream/sdk/server";
7979

8080
const pd = createBackendClient({
8181
environment: {development | production},
82-
projectId: {your_pipedream_project_i_d},
82+
projectId: {your_pipedream_project_id},
8383
credentials: {
8484
clientId: {your_oauth_client_id},
8585
clientSecret: {your_oauth_client_secret}

docs-v2/pages/connect/mcp/openai.mdx

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,6 @@ const pd = createBackendClient({
101101
// For this example, we'll use Notion
102102
const apps = await pd.getApps({ q: "notion" });
103103
const appSlug = apps.data[0].name_slug; // e.g., "notion",
104-
const appLabel = apps.data[0].name; // e.g., "Notion"
105104

106105
// Get access token for MCP server auth
107106
const accessToken = await pd.rawAccessToken();
@@ -118,7 +117,7 @@ const response = await client.responses.create({
118117
tools: [
119118
{
120119
type: 'mcp',
121-
server_label: appLabel,
120+
server_label: appSlug,
122121
server_url: `https://remote.mcp.pipedream.net`,
123122
headers: {
124123
Authorization: `Bearer ${accessToken}`,

docs-v2/pages/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ import VideoPlayer from "@/components/VideoPlayer";
44

55
Pipedream is the easiest way to automate any process that connects APIs:
66

7-
- Build and run workflows with code-level control when you need it, and no code when you don't in a [visual builder](/workflows)
8-
- Easily add thousands of customer-facing integrations to your app or AI agent in minutes with [Pipedream Connect](/connect)
7+
- [Pipedream Connect](/connect) makes it easy to add thousands of customer-facing integrations to your app or AI agent in minutes
8+
- Our [visual builder](/workflows) lets you build and run complex workflows with code-level control when you need it, and no code when you don't
99

1010
The Pipedream platform includes:
1111

docs-v2/pages/pricing/index.mdx

Lines changed: 33 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -2,91 +2,71 @@ import Callout from '@/components/Callout'
22

33
# Plans and Pricing
44

5-
We believe anyone should be able to run simple, low-volume workflows at no cost, and we want you to be able to prototype and get to value before having to pay Pipedream any money. We also hope that you share your [sources](/components/contributing/#sources), [workflows](/workflows/building-workflows/), [actions](/components/contributing/#actions), and other integration components so that other Pipedream users benefit from your work.
5+
We believe anyone should be able to run simple, low-volume workflows at no cost, and whatever you're building, we want you to be able to prototype and get to value before having to pay Pipedream any money. We also hope that you share your [sources](/components/contributing/#sources), [workflows](/workflows/building-workflows/), [actions](/components/contributing/#actions), and other integration components so that other Pipedream users benefit from your work.
66

7-
To support these goals, Pipedream offers a generous [free plan](#free-plan), free access to Pipedream Connect [while in `development`](/connect/environments), and you can **[request a free trial of our Advanced plan](https://pipedream.com/pricing)**. You can run sources and workflows for free within the limits of the free plan. If you hit these limits, you can upgrade to one of our [paid plans](#paid-plans).
7+
To support these goals, Pipedream offers a generous [free plan](#free-plan), free access to Pipedream Connect [while in `development`](/connect/environments), and you can **[request a free trial of our Advanced plan](https://pipedream.com/pricing)**. If you exceed the limits of the free plan, you can upgrade to one of our [paid plans](#paid-plans).
88

99
[Read more about our plans and pricing here](https://pipedream.com/pricing).
1010

1111
## Free plan
1212

13-
Workspaces on the Free plan have access to many of the Pipedream features including Workflows and Connect. However, the free plan includes several limitations:
13+
Workspaces on the Free plan have access to many of the Pipedream features including [Workflows](/workflows) and [Connect](/connect). However, the free plan includes several limitations:
1414

1515
**General:**
1616
- **Daily credit limit**: Free workspaces have a [daily limit of free credits](/workflows/limits/#daily-credits-limit) that cannot be exceeded
17-
- **Support**: Community support only via [our forum](https://pipedream.com/community) and Slack
18-
19-
**Workflows:**
20-
- **Connected accounts**: Limited to 3 different service accounts (like Slack, Google Sheets, GitHub, etc.)
21-
- **Active workflows**: Limited number of active workflows
22-
- **Polling intervals**: Triggers that poll for updates are limited to a lower frequency compared to paid plans
17+
- **Support**: Community support is available via our [community forum](https://pipedream.com/community) and [Slack](https://join.slack.com/t/pipedream-users/shared_invite/zt-36p4ige2d-9CejV713NlwvVFeyMJnQPwL)
2318

2419
**Connect:**
2520
- **Development environment**: Access all the features of Connect while in [development mode](/connect/environments)
2621

27-
To lift the daily credit limit and increase the number of workflows and connected accounts, [upgrade to a paid plan](https://pipedream.com/pricing).
28-
29-
## Paid plans
22+
**Workflows:**
23+
- **Active workflows**: Limited number of active workflows
24+
- **Connected accounts**: Limited number of connected accounts (like Slack, Google Sheets, GitHub, etc.)
3025

31-
[Visit our pricing page](https://pipedream.com/pricing) to learn more about our paid plans.
26+
To lift the daily credit limit, access additional features, or use Connect in production, [upgrade to a paid plan](https://pipedream.com/pricing).
3227

33-
All paid plans vary features based on plan level, but each paid plan option will:
28+
## Paid plans
3429

35-
- Remove the daily [credits](#credits) limit for both Workflows and Connect usage
36-
- Increase the number of active workflows available
37-
- Increase the number of connected accounts
38-
- Unlock full Connect production features with higher usage limits
39-
- Provide priority support options
30+
[Visit our pricing page](https://pipedream.com/pricing) to learn more about the details of our paid plans.
4031

4132
## Pipedream Connect
4233

43-
Pipedream Connect provides SDKs and APIs to let you easily add {process.env.PUBLIC_APPS}+ integrations to your app or AI agent. Connect uses the same credit-based pricing model as Workflows, with some key differences in how credits are consumed.
34+
Pipedream Connect provides SDKs and APIs to let you easily add {process.env.PUBLIC_APPS}+ integrations to your app or AI agent. Connect pricing is based on two inputs:
4435

45-
{/* todo: talk about external users */}
36+
1. **[API usage](#how-credits-work-in-connect)**: Credits consumed by action executions, tool calls, and other operations
37+
2. **[End users](#end-users)**: Referred to as "external users" throughout the docs and API, this is the number of unique users in your application who connect accounts
4638

4739
### How credits work in Connect
4840

49-
Here's how credit usage works in Connect:
41+
API operations that consume credits (1 credit per 30 seconds of compute time):
5042

51-
- **`runAction()`** - Consumes 1 credit per call
52-
- **`makeProxyRequest()`** - Consumes 1 credit per call
53-
- **Deployed triggers** - Consume 1 credit per invocation
54-
- For polling triggers: 1 credit each time the trigger checks for changes (based on your defined polling schedule/interval)
55-
- For webhook triggers: 1 credit each time an event is received
43+
- **Action executions**
44+
- **Tool calls via MCP**
45+
- **Source execution for deployed triggers**
46+
- **Requests to the Connect proxy**
5647

57-
<Callout type="info">
58-
We don't charge credits for API calls that help you manage integrations, such as:
59-
- `getAccounts()` - List connected accounts
60-
- `getApps()` - Get available apps
61-
- `getComponents()` - List components
62-
- `configureComponent()` - Configure component settings
63-
- Other management and configuration endpoints
64-
</Callout>
48+
API operations that do **not** consume credits:
6549

66-
### Connect credit examples
50+
- **Listing apps, actions, and triggers**
51+
- **Listing accounts**
52+
- **Configuring actions and triggers**
53+
- **Other management operations**
6754

68-
| Scenario | Credits Used |
69-
| --- | --- |
70-
| Running a Slack "Send Message" action via `runAction()` | 1 credit |
71-
| Making an authenticated API request via `makeProxyRequest()` | 1 credit |
72-
| Polling trigger checking for new GitHub issues every 5 minutes | 1 credit per check (12 per hour) |
73-
| Webhook trigger receiving a Stripe payment event | 1 credit per event |
74-
| Calling `getAccounts()` to list user's connected accounts | 0 credits |
75-
| Configuring a component with `configureComponent()` | 0 credits |
55+
### End users
7656

77-
### Connect pricing considerations
57+
End (external) users are a core billing component for Connect pricing, separate from credit usage:
7858

79-
- Credits are consumed at the workspace level, shared across both Workflows and Connect usage
80-
- The same [free plan](#free-plan) and [paid plans](#paid-plans) limits apply
81-
- Monitor your Connect usage in your [Billing and Usage Settings](https://pipedream.com/settings/billing)
59+
- **End user definition**: A unique end user in your application who connects one or more accounts through Connect
60+
- **User to account relationship**: Each end user can have multiple connected accounts (e.g., one user might connect their Slack, Gmail, and GitHub accounts)
61+
- **Billing impact**: For standard plans, you're billed based on the number of unique external users, not the number of connected accounts
8262

8363
## Pipedream Workflows
8464

8565
Pipedream Workflows uses a credit-based pricing model where you pay for compute time used during workflow execution.
8666

8767
### Credits and billing
8868

89-
Pipedream uses a number of terms to describe platform metrics and details of our plans. See the definitions of key terms below.
69+
Pipedream uses a number of terms to describe platform metrics and details of our plans. See the definitions of key terms in the [glossary](/glossary).
9070

9171
#### How credits work for Workflows
9272

@@ -96,7 +76,7 @@ Unlike some other platforms, Pipedream does not charge for usage based on the nu
9676

9777
Adding additional memory capacity to workflows will increase credit usage in intervals of 256 megabytes. For example, doubling the memory of a workflow from 256MB to 512MB will double the cost of credits in the same execution time.
9878

99-
##### Scenarios
79+
**Scenarios**
10080

10181
<Callout type="info">
10282
Developing a workflow with test events in the Pipedream workflow builder is free. No credit usage is incurred.
@@ -106,7 +86,7 @@ Developing a workflow with test events in the Pipedream workflow builder is free
10686
If an active workflow isn't executed in a billing period no credit usage is incurred. Pipedream only charges credits for workflow executions.
10787
</Callout>
10888

109-
###### Workflow segments configured to use 256MB memory (default)
89+
**Workflow segments configured to use 256MB memory (default)**
11090

11191
| Scenario | Credits Used |
11292
| --- | --- |
@@ -117,7 +97,7 @@ If an active workflow isn't executed in a billing period no credit usage is incu
11797
| Workflow with a branch - 3 seconds before the branch- 15 seconds within the executed branch | 2 credits |
11898
| Workflow with a branch - 3 seconds before the branch, 15 seconds within the executed branch, 3 seconds after the branch in the parent flow | 3 credits |
11999

120-
###### Workflow segments configured to use 1GB memory
100+
**Workflow segments configured to use 1GB memory**
121101

122102
| Scenario | Credits Used |
123103
| --- | --- |
@@ -128,7 +108,7 @@ If an active workflow isn't executed in a billing period no credit usage is incu
128108
| Workflow with a branch - 3 seconds before the branch- 15 seconds within the executed branch | 8 credits |
129109
| Workflow with a branch - 3 seconds before the branch, 15 seconds within the executed branch, 3 seconds after the branch in the parent flow | 24 credits |
130110

131-
##### Source credit usage
111+
#### Source credit usage
132112

133113
When an [event source](/workflows/building-workflows/triggers/) triggers a workflow, **the source execution is included for free.** This includes workspaces on the [Free Tier](/pricing/#free-tier).
134114

pnpm-lock.yaml

Lines changed: 6 additions & 8 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)