Uploaded August 2026 | Updated September 2026, 11 hours ago

---

There's a point where a provider access token exists in plain text inside your app — where it can be looked at, logged, or leaked. Even if you're using a credential manager like WorkOS Pipes.

WorkOS Relay removes that moment entirely. Send the request to WorkOS, Relay attaches the user's credential server-side, and the provider's response streams back. The credential never leaves WorkOS — built for AI agents and other untrusted runtimes.

In this video:
• Where token-based integrations expose you
• How Relay proxies requests so tokens never enter your app
• A live migration, done by a coding agent pointed at the docs

Relay is in early access. Contact WorkOS support to request access.

Relay docs: workos.com/docs/pipes/relay
WorkOS Pipes: workos.com/docs/pipes
Supported providers: workos.com/docs/pipes/relay#supported-providers

Chapters:
0:00 The quiet data security nightmare
0:36 How Pipes integrations work today
1:19 Keep tokens out of your app with Relay
1:41 Demo: Add Relay to a Pipes app
2:19 Relay enabled — no exposed token
2:28 Migrating with a coding agent
3:12 Is Relay for you?