Migrating from Pipedream Connect
How Pipedream Connect's external users and connected accounts map to Arc0, whether tokens can move, and the free migration offer.
Pipedream Connect and Arc0 both let your users authorize an app once and give your agent access to it afterward. This page maps the concepts and covers what moving over involves.
How the concepts map
| Pipedream Connect | Arc0 |
|---|---|
| External user | Connected user |
| Connected account | Connection |
| App | App |
An external user is how you identify your own end user to Pipedream, the same role an external id plays for an Arc0 connected user. A connected account is that user's authorized account in a given app, which Arc0 calls a connection. Pipedream Connect's catalog is organized by API and by the tools and triggers built on it; Arc0's catalog is organized by app, with each action graded read, write or destructive so a policy can decide what runs.
Can you move your tokens?
If your Pipedream accounts use your own OAuth apps and Pipedream's API can export the underlying tokens, those connections can move into Arc0 without a reconnect. Otherwise, your users reconnect once, through Arc0 Connect, which carries your brand and, on paid plans, your own domain.
Staging the reconnect
Point new users at Arc0 Connect from the start, and prompt existing users to reconnect the next time their agent needs that app, rather than all at once. Reconnecting is also the moment to move a connected account off a Pipedream-managed OAuth app and onto your own, if you want the provider's consent screen to name you going forward. An engineer helps set this up as part of the free migration — see Migrating to Arc0.
Swapping your agent's calls
Point your MCP client at your Arc0 MCP endpoint, https://mcp.arc0.ai/u/{user}, or swap the SDK
call that runs an action for arc0.actions.run('gmail.send_email', { user, input }), and set
read, write and destructive rules for each app in Policies. See
Arc0 MCP and SDK.
The offer
Every Arc0 plan includes a free, engineer-led migration, covering the mapping above and the staged reconnect.
Contact us to start your migration.