Skip to main content
VPCs in Pipedream Connect let you send tool calls from a dedicated network with a static egress IP address that’s unique to your workspace. Once you assign a VPC to a Connect project, its action executions (tool calls) and trigger executions send their outbound traffic from the VPC’s static IP. This is useful when an upstream app restricts access by IP allowlist — for example Jira, GitHub Enterprise, Salesforce, databases, or internal APIs. You (or your customers) can add the project’s static IP to those allowlists so requests are accepted.

​
How it works

  1. Create a VPC in your workspace and wait for it to finish provisioning (this may take 5–10 minutes)
  2. Assign the VPC to a Connect project
  3. That project’s tool calls and triggers now egress from the VPC’s static outbound IP
  4. Add that IP to the allowlists of any upstream apps or resources that have IP restrictions
What routes through the VPC: action executions (tool calls), including the remote-options and reload-props requests that configure them, and trigger executions and emits. Connect API Proxy requests don’t — they egress from Pipedream’s shared network pool. Account connections come from a separate static block, 44.223.89.56/29.

​
Getting started

​
Create a VPC

VPCs are managed at the workspace level. In your Connect dashboard, open your workspace Settings → Networking. This page lists every VPC in your workspace along with its name, status, static outbound IP, assigned project, and creation date.
1

Create the VPC

Click Create VPC, enter a name, and create it.
2

Wait for provisioning

Provisioning takes roughly 5–10 minutes. The status moves from Provisioning to Ready. A VPC can only be assigned to a project once it’s Ready.
If provisioning ends in a Failed state, the VPC can only be deleted — failed VPCs don’t count against your plan’s VPC limit.

​
Assign a VPC to a project

A VPC does nothing until it’s assigned to a project. You can assign one from either entry point:
  • From the project: open the project’s Configuration and select Networking. Use the network dropdown to choose a Ready VPC instead of the default Pipedream Shared Network Pool (the set of egress IPs shared across all workspaces that haven’t assigned a VPC).
  • From workspace settings: in Settings → Networking, open a VPC’s Edit dialog and select the project to assign it to.
Once assigned, the project’s Networking page shows the VPC’s status and its static outbound IP.
Assignment is strictly 1:1: a VPC can be assigned to at most one project, and a project can have at most one VPC. Assigning a VPC to a project that already has a different VPC replaces the existing assignment.

​
Find and copy the static outbound IP

Your VPC’s static outbound IP is shown (with click-to-copy) both in Settings → Networking and on the assigned project’s Networking page. When adding it to an upstream allowlist, use the /32 CIDR block to allow the single address. The IP is assigned by Pipedream and can’t be changed or chosen.

​
Managing VPCs

Manage VPCs from Settings → Networking in your workspace:
  • Rename a VPC or reassign it to a different project from its Edit dialog.
  • Delete a VPC. You’ll be asked to type the VPC’s name to confirm.

​
Limitations

  • VPCs provide a static IP for outbound traffic only. This feature does not provide a static inbound IP or otherwise restrict inbound requests.
  • Provisioning a new VPC can take up to ~5–10 minutes. A VPC can’t be assigned to a project until it reaches the Ready state.
  • Connect API Proxy requests don’t route through the VPC — see What routes through the VPC.

​
Pricing

VPCs are available on the Business plan, with a maximum number of VPCs per workspace. Visit the pricing page to upgrade, or reach out to our team if you need more VPCs.

​
FAQ

​
Can I change or choose my VPC’s IP address?

No. IP addresses are assigned by Pipedream and are not changeable.

​
Can a VPC be assigned to more than one project?

No. Assignment is 1:1 — one VPC per project, and one project per VPC. Reassigning a VPC to a new project replaces its previous assignment.