Uploaded July 2026 | Updated November 2026, 2 days ago
This video walks through WorkOS Pipes, a feature that lets you add OAuth connections — GitHub, Slack, Google, and more — to your app without writing and maintaining all the integration plumbing yourself. It's aimed at developers building apps that need to connect to third-party services, including AI agent workflows.
Starting from a blank integrations page in a React Router project, the demo covers installing the WorkOS Pipes widget using WorkOS MCP agent skills, configuring a GitHub OAuth app, handling CORS in the WorkOS dashboard, and displaying live GitHub user data once the connection is established.
The video also shows a real internal use case: the WorkOS team's own YouTube publishing tool, which uses Pipes to connect Google and X accounts, generate metadata from transcripts, and push content directly to those platforms via OAuth.
If you're building multi-tenant apps or agentic tools that need to act on behalf of users across external services, Pipes handles the OAuth complexity so you don't have to.
Links:
- workos.com/pipes
- workos.com/docs/pipes
Chapters:
0:00 Why OAuth integrations are painful
0:26 What WorkOS Pipes does
0:50 Adding the Pipes widget with MCP
1:33 Handling CORS in the WorkOS dashboard
2:12 Connecting a GitHub OAuth app
3:08 Testing the live GitHub connection
3:26 Displaying GitHub user data
3:52 Real-world use: WorkOS YouTube publishing tool
This video walks through WorkOS Pipes, a feature that lets you add OAuth connections — GitHub, Slack, Google, and more — to your app without writing and maintaining all the integration plumbing yourself. It's aimed at developers building apps that need to connect to third-party services, including AI agent workflows.
Starting from a blank integrations page in a React Router project, the demo covers installing the WorkOS Pipes widget using WorkOS MCP agent skills, configuring a GitHub OAuth app, handling CORS in the WorkOS dashboard, and displaying live GitHub user data once the connection is established.
The video also shows a real internal use case: the WorkOS team's own YouTube publishing tool, which uses Pipes to connect Google and X accounts, generate metadata from transcripts, and push content directly to those platforms via OAuth.
If you're building multi-tenant apps or agentic tools that need to act on behalf of users across external services, Pipes handles the OAuth complexity so you don't have to.
Links:
- workos.com/pipes
- workos.com/docs/pipes
Chapters:
0:00 Why OAuth integrations are painful
0:26 What WorkOS Pipes does
0:50 Adding the Pipes widget with MCP
1:33 Handling CORS in the WorkOS dashboard
2:12 Connecting a GitHub OAuth app
3:08 Testing the live GitHub connection
3:26 Displaying GitHub user data
3:52 Real-world use: WorkOS YouTube publishing tool






![Vibe-Coded Internal Apps, Shipped Securely in Minutes - Jacobia Johnson, WorkOS | init() 2026
Vibe-Coded Internal Apps, Shipped Securely in Minutes - Jacobia Johnson, WorkOS | init() 2026
## Description
Its day one at a new job. You vibe-code a Customer 360 app, share it with the team, and IT tells you to take it down immediately. In this live demo from the init() 2026 keynote, WorkOS engineer Jacobia Johnson has Codex deploy that prototype to WorkOS Atlas and ships it securely the same day. (Acme, Sandy, and Mark are a fictional demo scenario.)
Atlas is a platform for building, securing and sharing AI-built internal apps. In this demo it provides:
- Authentication shared across every app (sign out once, signed out everywhere)
- OAuth data connectors (Snowflake, Salesforce, Stripe, Linear, Slack, OpenAI in the demo). Apps stop working when a connection is removed.
- A provisioned database for app data
- An AI gateway with AI spend tracking
- Access control using groups from your identity provider
- Activity/audit logs, usage analytics, and an app directory
- A Slack bot, connected to your tools via MCP
Atlas is a preview, rolling out over the coming weeks and months.
🔗 Learn more about WorkOS Atlas: [ATLAS LINK]
▶️ Watch the full init() 2026 keynote with Michael Grinich: https://www.youtube.com/watch?v=syCdTSqB1To
0:00 Day one at Acme: the Customer 360 idea
1:17 The vibe-coded prototype
2:42 Shipping it live… and getting shut down
3:36 ITs requirements: auth, OAuth, audit logs, AI spend
4:22 Deploying to Atlas with Codex
5:08 The Atlas app directory
5:38 A live app: Deal Health
6:39 OAuth data connectors
7:36 Access control with IdP groups
9:00 Audit logs
9:32 Moment of truth: the deployed app
11:34 Analytics and AI spend
12:30 Shared sign-in across apps
12:58 Atlas in Slack
#WorkOS #Atlas
## Tags
WorkOS, WorkOS Atlas, Atlas, init() 2026, init 2026, WorkOS init, vibe coding, vibe coded apps, internal tools, internal apps, AI internal tools, Codex, coding agents, AI agents, Customer 360, shadow IT, enterprise security, authentication, OAuth, data connectors, access control, identity provider, IdP groups, audit logs, AI gateway, AI spend, MCP, Slack bot, Jacobia Johnson, developer tools Vibe-Coded Internal Apps, Shipped Securely in Minutes - Jacobia Johnson, WorkOS | init() 2026](https://i.ytimg.com/vi/UZw5BEwlu7Y/mqdefault.jpg)



