ooligo

Pipedream

agent-integration-platform mcp-gateway · agent-authentication · embedded-integrations · tool-calling
AI-NATIVE MCP API FREEMIUM
RevOpsLegal OpsRecruiting & TACustomer Success
7.2 /10

What it is

Pipedream is now two different answers depending on which product you bought. Workday signed the agreement to acquire it on 19 November 2025, and the deal closed in February 2026. In 2026 Pipedream put its original product, Workflows, into maintenance mode along with its String agent builder. Both shut down on 31 March 2027. Pipedream Connect is the product that carries on, and the docs say Connect “is where our focus is going forward”.

Connect is a developer toolkit for adding third-party integrations to your own app or AI agent. It does three jobs. Managed auth: your end users connect their Gmail, Salesforce or HubSpot account through Connect Link or the client SDK, and Pipedream stores and refreshes the tokens. Tools: 10,000+ prebuilt actions and triggers across 3,000+ APIs, callable from your code. MCP: the same tools exposed as a remote MCP server at remote.mcp.pipedream.net, so Claude, Cursor or your own agent can call them without you writing a server. SDKs ship for TypeScript, Python and Java, plus a REST API. A Connect proxy lets you make raw authenticated requests to any endpoint a prebuilt action does not cover.

Pipedream says it does not store API request payloads or response bodies, and holds SOC 2 Type 2 and GDPR on every plan. HIPAA with a BAA, SSO and SCIM are on Business only.

The fork it resolves

The question this page answers is the one the acquisition created: is Pipedream still safe to build agent integrations on, or do you move?

The answer splits cleanly by product. If you run Pipedream Workflows, you are moving. The decision is only where to and when. Workflows takes no new signups or subscriptions. Subscriptions are cancelled on 31 March 2027 with a prorated refund, and all Workflows data is deleted by 30 April 2027. Connect is not a replacement. It is an integration layer you call from your own runtime, not a hosted scheduler that runs your Node.js and Python steps.

If you build on Connect, the product is live and getting the investment. The risk is the owner. Workday is an HR and finance suite that bought Pipedream, Sana and Flowise in the same cycle to feed its own agent platform. Flowise announced its own shutdown in summer 2026, and Workflows followed. Connect is the piece that fits Workday’s agent plan, which is the best argument for its survival and also the reason its roadmap will answer to Workday’s needs before yours.

Pricing reality

Connect pricing has two meters: external users and credits.

  • Free — $0, no card. Every feature, unlimited team members, but external users and credits are development only. You cannot run production traffic on it.
  • Startup — $99 a month billed annually; the page shows $150 for month-to-month. Includes 100 external users, then $2 per user, and 10,000 credits, then $0.012 per credit. Email support.
  • Business — custom, annual billing. Adds SSO, SCIM, HIPAA, dedicated static egress IPs, SLAs and a dedicated Slack channel, plus volume pricing on both meters.

An external user is anyone who has connected at least one account; one user with five connected apps counts once. Actions, MCP tool calls, proxy requests and trigger events each cost 1 credit per 30 seconds of compute. Management API calls are free.

Work it through for a typical production agent: 500 end users and 50,000 tool calls a month, each finishing inside 30 seconds. That is $99 + 400 × $2 + 40,000 × $0.012 = $1,379 a month. Two-thirds of the bill is the 500 users and their tool calls, not the platform fee. Against the peers on our site, $0.012 per call is 40x Composio’s $0.0003, roughly level with Arcade’s $0.01, and about a third of Merge’s Pro plan ($1,000 for 25,000 credits, about $0.04 each). Pipedream is the only one of the four that also charges per end user.

Best for

The product engineer at a B2B SaaS company embedding integrations into their own product, where each customer connects their own accounts and the breadth of the catalogue decides deals. Concrete case: a recruiting or RevOps product whose AI assistant must act in whichever CRM, ATS or inbox each customer uses, across a long tail of 200+ apps nobody wants to build OAuth for, at a few hundred customer accounts.

Not for

Internal agents run by your own ops team. Your 15 RevOps analysts do not need white-labelled Connect Link or a per-end-user meter, and Composio does that job at a fraction of the per-call price. It is also wrong for anyone looking for a hosted workflow runner: that product is closing.

Versus the alternatives

  • Composio — the low-cost per-call pick for agent tool-calling, from $29 a month plus $0.0003 per call, SOC 2 and ISO 27001. Pick it for internal or high-volume agents where per-call cost dominates and you do not need per-customer branded auth.
  • Merge Agent Handler — the enterprise-governance pick, Pro at $1,000 a month. Pick it when security review wants tool-level permissions, audit and DLP over every agent call, and the API list is the mainstream enterprise SaaS set.
  • Arcade — the fastest-growing entrant by funding, $60M Series A in June 2026, Team at $25 a month plus $0.01 per call. Pick it when per-user authorization of each tool call is the hard part, and you want a vendor not owned by a suite company.
  • For Workflows migrants: n8n or Activepieces. n8n is the closest like-for-like for code steps, triggers and a large catalogue, from about $23 a month or self-hosted. Activepieces is the MIT-licensed option when you want no single owner able to take the runner away again.

If none fit, and you integrate with fewer than about ten APIs, write the OAuth flows yourself. Ten integrations is a quarter of one engineer’s time. A per-user meter on top of that is a permanent tax.

Watch-outs

  • Workflows deletion is a hard deadline with credentials attached. Everything stops on 31 March 2027, and all Workflows data, connected accounts included, is gone by 30 April. Guard: export every workflow’s code and inventory every inbound webhook URL and schedule now. Point upstream systems at the replacement’s endpoints before March, and re-authorize each connected account in the new tool rather than assuming a token export.
  • Your end users’ tokens live in a Workday-owned vault. If you leave Connect, every customer re-authorizes every account. Guard: register your own OAuth clients (Custom OAuth clients are on every plan) so the consent screen and app registration are yours. Keep Connect behind your own integration interface, and on Business negotiate a change-of-control notice period and a data-export clause.
  • The per-user meter grows with your customer base, not your usage. At 2,000 connected users, Startup’s user line alone is $3,800 a month before a single credit. Guard: model both meters at 12-month projected customer counts before you sign, and get Business volume pricing in writing once you cross a few hundred users.
  • Credits are compute time, so slow APIs cost double. A tool call that waits 31 seconds on a sluggish upstream API costs 2 credits. Guard: set timeouts on every action, and alert on credits per tool call rising above 1.2 in the usage dashboard. That ratio is the early sign of a degraded upstream.