Nango vs WorkOS Pipes and Agents

Nango

1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan.

WorkOS Pipes and Agents

Agent identity with per-session revocation and token lifetimes set per blueprint. 21 incidents on the status page since 3 July 2026, several over an hour.

Nango

1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
2. Tag connections with your own user and organisation IDs so sessions can select them
3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
4. Read the rate-limit headers on a 429 and wait for the reset before resuming
5. Run 0.71.6 or later when self-hosting, and keep the runner port off the network

WorkOS Pipes and Agents

1. Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token
2. Branch on active in the response and send the user to reconnect on needs_reauthorization
3. Wait for Retry-After on a 429, or back off with jitter when it's missing
4. Use lower-case provider slugs such as github or slack
5. Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry