Skip to main content
The Pipedream connector gives a workspace tools for thousands of SaaS apps — Slack, Google Workspace, Notion, GitHub, and the rest of the Pipedream catalog — with authentication to each app managed by Pipedream Connect. Users connect their own accounts through a consent flow; Pipedream stores those credentials in its vault and executes each app’s API; Conduit decides who may use which app and tool, and records every call. A workspace admin connects Pipedream once per workspace, from any Pipedream app’s Connection tab on Home.

Setup

You need a Pipedream workspace with Connect and a project in it. From its API settings, create OAuth client credentials — one pair per Conduit workspace. Then, on Home, open any app and go to its Connection tab, which offers Connect Pipedream until it’s connected. Enter:
  • Client ID and secret — the secret is write-only and stored encrypted, like every credential Conduit holds.
  • Project ID and environment (development or production).
That’s the whole registration — there is nothing else to register on the Pipedream side. Saving runs a connectivity check and reports the result, and distinguishes bad client credentials from a project the credentials can’t use. Once connected, the cog on the Pipedream choice of every app’s Connection tab opens the workspace’s Pipedream settings, to replace the credentials or turn Pipedream off for the workspace. Turning it off keeps the credentials and who each app is allowed for; nobody can use a Pipedream app until it’s connected again. Individual apps become available to people through access policies: an app’s Access tab grants it to everyone, a group or a person, the way you’d grant any connector. You can also grant all apps on Groups & Policies and let people enable what they need.

How Conduit authenticates to Pipedream

Conduit exchanges the workspace’s client credentials at Pipedream’s token endpoint for a short-lived, workspace-scoped access token, caches it, and re-mints it as needed — the standard OAuth client-credentials grant. This token authenticates Conduit itself (tool listing and calls, the app catalog, account management); it is never handed to browsers or AI clients.

How users connect their app accounts

Each person connects their own app accounts, from Home — or directly from their AI client, which guides them to the same place:
  1. Conduit mints a short-lived, single-use Connect token scoped to the user and hands it to the browser.
  2. The browser opens Pipedream’s connect flow, where the user authorizes the app on the app’s own consent screen (standard OAuth between Pipedream and the app).
  3. Pipedream stores the resulting credential in its vault, keyed to the user’s Conduit identity. Conduit then verifies with Pipedream that the account actually exists — the browser’s word is not trusted — and refreshes the user’s tool lists.
App credentials therefore live in Pipedream’s vault, not in Conduit’s database, and never pass through the AI client. Users see their connected accounts — with health status — on the Accounts page and can disconnect them there; disconnecting revokes the stored credential.

Setting how people connect an app

As a workspace admin, open an app on Home and go to its Connection tab. It shows what people are asked when they connect the app: how they sign in (OAuth, or credentials they enter) and each field Pipedream’s connect window asks for, such as an instance name. From there you can decide some of it for them:
  • Set for everyone (or Choose for everyone, for a choice) fills a field in once, so people aren’t asked for it. A secret field can’t be filled in: each person enters their own. A text field named like a credential warns that filling it in shares one credential with everyone.
  • OAuth client: Pipedream’s, or Bring your own. To bring your own, select Get the redirect URI and register it when you create the OAuth app with the provider, then enter the client ID, the secret and, optionally, scopes; left blank, Conduit copies in the scopes Pipedream’s own client asks for when you save (later changes to Pipedream’s defaults don’t follow; an app Pipedream has no client for has none, so the provider applies its own). The secret is write-only. A new client ID registers a new OAuth client, so it needs its secret too. If the app doesn’t take your own OAuth client, Conduit says so and keeps Pipedream’s. Where Pipedream has no OAuth client for an app, people can’t connect it until you bring your own, so allowing the app opens Connection first.
  • Reset to Pipedream’s defaults removes both.
Conduit saves these in your Pipedream project, as an app override and an OAuth client, and keeps only their ids: field values and the client secret are stored in Pipedream, not in Conduit. Every connect and reconnect applies them: Conduit asks Pipedream for connect tokens pinned to your OAuth client, and Conduit’s connect window applies the client and the field values. Pipedream doesn’t check a connect token’s app or OAuth client: a token Conduit issues for your client can still open the connect window for another app or client. So don’t rely on either to restrict what people connect to. People already connected keep their connection until they reconnect. If someone deletes the override or the client in Pipedream, people connect with Pipedream’s defaults again.

How tool calls carry identity

When a user’s client calls an app tool, Conduit forwards the call to Pipedream’s MCP endpoint with headers identifying the workspace’s project and environment, the calling user, and the apps the caller’s policy resolution permits. Pipedream uses the user identity to fetch that user’s credential from its vault — so every call executes as the person who made it, and one user’s Slack tools can never post as another’s. These headers are set by Conduit from workspace configuration and the authenticated session, on every call. They cannot be overridden: connector configuration rejects header names in the gateway-identity namespace, so neither an admin nor anyone else can supply a different user or project by configuration.

Network path

Conduit reaches exactly two Pipedream hosts — the API (token minting, Connect tokens, account management, the app catalog) and the MCP endpoint (tool listing and calls) — and each user’s browser loads the connect flow from pipedream.com. Network Access lists all of them precisely, and the private-endpoints guide covers consuming both hosts over a private endpoint such as AWS PrivateLink — supported at the application level with one environment variable.

Observability

Pipedream app calls are first-class citizens of Conduit’s governance: each call is policy-checked before it leaves, recorded in usage dashboards under its full tool name (a denied call also lands in the audit log), traced end to end, and counted in the per-connector metrics. Nothing about the managed-auth path bypasses the gateway’s controls.