Pipedream

More than 10,000 prebuilt tools across 3,000+ APIs reach an agent through Pipedream Connect, with fully managed OAuth and per user credentials encrypted at rest, as prebuilt actions, through an MCP server for every app, or as raw API calls through the Connect proxy with tokens injected per user; customers publish their own custom tools beside the catalog.

Sourcepipedream.com/docs/connect/mcpread 2026-09-22

Control flow in Pipedream Workflows is documented: steps sequence prebuilt actions and Node.js, Python, Go or Bash code, with if/else, switch, parallel branches, delay, filter and end, plus concurrency and throttling settings, error handling, and suspend, resume and rerun for long running or externally gated steps.

Sourcepipedream.com/docs/workflows/building-workflows/control-flowread 2026-09-22

No retrieval, document ingestion, index or semantic search over the customer's content is documented. Data stores and file stores hold records and files that workflow code reads by key, and the integrations query other systems live, but no RAG layer of the product's own grounds work in company data.

Sourcepipedream.com/docs/llms.txtread 2026-09-22

A workflow can stop for a person: $.flow.suspend pauses an execution until someone manually approves or cancels it, returning resume and cancel links the workflow can send by email or to any service, and paused executions are listed in Event History. Project access controls limit who can see and edit workflows.

Sourcepipedream.com/docs/workflows/building-workflows/code/nodejs/rerunread 2026-09-22

SOC 2 compliance is demonstrated through annual third party audits, Pipedream states, with a SOC 2 Type 2 report on request, a published Drata security report, HIPAA BAAs and a GDPR Data Protection Addendum. On the access side it documents single sign on through Google Workspace, Okta or any SAML provider, domain verification, and project level access controls, and Connect credentials are encrypted at rest and never exposed to models.

Sourcepipedream.com/docs/privacy-and-securityread 2026-09-22

Each run is recorded. The inspector lists every event a workflow received with its incoming data and execution logs, which can be replayed, and Event History shows all workflow executions across a workspace with stack traces, filterable by status (including errors and paused runs), workflow and time. The REST API returns workflow errors and emits, Connect lists recent trigger events and usage records, and event history is retained for a stated period by plan. An audit log and SIEM export are not documented.

Sourcepipedream.com/docs/workflows/event-historyread 2026-09-22

Data stores persist JSON records across workflow executions, scoped to the workspace, readable and writable from workflow code and editable in the dashboard, with an optional time to live per record or no expiry, and plan limits stated. A workflow reads that store as context on its next run. It is a general key value store rather than memory built for agents, and records are not atomic across concurrent workers.

Sourcepipedream.com/docs/workflows/data-management/data-storesread 2026-09-22

Hosting is on AWS in the us-east-1 region, and Virtual Private Clouds run a workspace's workflows (and, separately, Connect tool calls) in a dedicated isolated network with static egress IPs unique to that workspace. That isolates the network on the hosted platform, but only one region is stated, and no region choice or self hosted option is documented.

Sourcepipedream.com/docs/privacy-and-securityread 2026-09-22

Prebuilt triggers and actions and the source available component registry are integration capability rather than packaged assets. Workflows can be shared as templates through a link, so one account can copy another's workflow, but the documentation carries no catalog of ready made workflows, templates or agents that Pipedream publishes for buyers to adopt.

Sourcepipedream.com/docs/workflows/building-workflows/sharingread 2026-09-22

Work starts without a person asking: workflows run on app event sources across the catalog, HTTP requests and schedules, and Connect lets a developer deploy triggers for its users' accounts that deliver each emitted event to the customer's webhook, with signed deliveries and a list of recent events per trigger.

Sourcepipedream.com/docs/connect/components/triggersread 2026-09-22

Pipedream serves its tools to whatever model the customer runs: its MCP guides cover the Vercel AI SDK, OpenAI, Anthropic and Google Gemini, any MCP client such as ChatGPT, Claude or Cursor can connect, and the model is chosen and keyed by the customer. Pipedream names no model of its own for these tools, so buyers bring their own providers and keys.

Sourcepipedream.com/docs/connect/mcpread 2026-09-22

Pipedream is callable from outside through the Connect API (apps, accounts, users, actions, triggers, projects, OAuth clients and usage) with TypeScript, Python and Java SDKs, a REST API for workflows, sources and webhooks with a published OpenAPI specification, and a CLI; it serves an MCP server for every integrated app, and developers publish custom components and tools to the registry.

Sourcepipedream.com/docs/connect/api-reference/introductionread 2026-09-22

Testing before release is covered: workflows can be built, configured and tested with an AI assistant, test events run steps in the builder free of charge, the inspector replays past events, and Connect separates development and production environments. No scored test cases, pass rate or other comparable result for evaluating a change is documented.

Sourcepipedream.com/docs/workflows/building-workflows/build-with-airead 2026-09-22

Pipedream ships its own @pipedream/browsers package that starts a Chromium instance inside its Node.js execution environment and hands a workflow step a Puppeteer or Playwright browser, documented for scraping, screenshots and programmatically interacting with websites, including JavaScript heavy ones. The browser is bundled and run by Pipedream's runtime, so a workflow drives a real browser through it.

Sourcepipedream.com/docs/workflows/building-workflows/code/nodejs/browser-automationread 2026-09-22