OAuth launch intelligence

Know the path
before you build.

Source-backed guides for setting up provider OAuth apps—what to do, how long it may take, and what can block approval.

GC
Example pathGoogle Calendar
High
✓
Choose narrow scopesAgent can prepare
2
Configure OAuth clientDeveloper action
3
Submit verificationProvider decision · typically 3–5 days*
Your next actionDecide: event details or free/busy only?
4 official sources
→ Clear handoffs

*Conditional published review estimate, not a guarantee.

Built for honest decisions before credentials, code, and review submissions.

Official sourcesExplicit unknownsAgent + human handoffs

Curated library · 3 guides

Start with a researched path

Each guide is tied to a specific capability and launch audience.

Moderate

Custom OAuth app; compare with a GitHub App first

GitHub

Let an agent work with a customer’s repositories

Hands-on effort
Not measured
External wait
Unknown — organization owner dependent

Main blockerThe repo scope may be broader than the product needs.

Open launch guide
High

Developer-owned web OAuth client

Google Calendar

Read customer event details for a meeting assistant

Hands-on effort
Not measured
External wait
Typically 3–5 business days when sensitive-scope verification applies

Main blockerMissing verified domain, privacy policy, or scope justification.

Open launch guide
Moderate

Custom Slack app with OAuth distribution

Slack

Post agent updates in customer workspaces

Hands-on effort
Not measured
External wait
Unknown for workspace admins; up to 10 weeks for Marketplace functional review

Main blockerTreating an unlisted pilot and Marketplace launch as the same path.

Open launch guide
Low

Custom Discord application with bot user and OAuth2

Discord

Let an agent post messages and respond to commands in customer Discord servers

Hands-on effort
10–20 mins
External wait
Instant for fewer than 100 servers; verification required at 100+ servers

Main blockerBots in 100+ servers must be verified by Discord, requiring a description of how you use privileged intents.

Open launch guide
Low

Custom OAuth application registered in Linear workspace settings

Linear

Let an agent create, read, and manage issues in a customer's Linear workspace

Hands-on effort
15–30 mins
External wait
Instant / Self-service

Main blockerYou must be a Workspace Admin in Linear to register OAuth applications, and the app must be toggled to Public to allow external workspaces.

Open launch guide
Moderate

Public integration created in the Notion Integrations portal

Notion

Let an agent read and write pages and databases in a customer's Notion workspace

Hands-on effort
20–40 mins
External wait
Instant for self-service; Notion Marketplace listing requires separate review

Main blockerNotion does not use traditional string scopes — users control access via a page picker during authorization. Your app can only access explicitly shared pages.

Open launch guide

From idea to launch

One guide. Every decision.

The setup form is only one part of readiness. We keep work, waiting, and ownership visible.

01

Choose the path

Compare managed OAuth, a provider-owned app, and the exact permissions your feature needs.

02

Prepare and test

Collect prerequisites, configure redirect URLs, and test the smallest real user connection.

03

Clear the gates

See review evidence, admin dependencies, likely blockers, and who has to act next.

Outside the library

Bring an unfamiliar app.

Enter a provider name or website. We'll first resolve what you mean, then research official OAuth sources.

01 Identify02 Investigate03 Build guide

Use public provider information only. Never enter client secrets or access tokens.