How long until your users can connect?
The problem
Before your agent can act in someone’s Gmail, Slack or CRM, you need your own OAuth app with that provider. Some take minutes. Others hold real users back behind weeks of review, security audits or partner programs, and you usually find out after you’ve built the integration.
What this gives you
A guide for each app: how hard it is, how long until it works in dev and until anyone can connect, which permissions trigger review, the steps (and which an agent can do for you), what blocks people, and links to the provider’s own docs. Every claim shows its evidence.
113 guides, popular first. All are agent-researched unless marked otherwise.
| Google (Gmail, Calendar, Drive) Email, calendar & files | Hard | Dev 30–90 min | Any user 6–10 weeks |
| Slack Communication | Hard | Dev 15–60 min | Any user 1–3 months |
| GitHub Developer tools | Trivial | Dev 15–60 min | Any user Same day |
| Microsoft (Outlook, Teams, OneDrive) Productivity suite | Hard | Dev 30–90 min | Any user 1–3 weeks |
| Notion Productivity / Docs | Trivial | Dev 15–60 min | Any user Same day |
| HubSpot CRM | Moderate | Dev 1–3 hours | Any user 2–6 weeks |
| Salesforce CRM | Moderate | Dev 30–90 min | Any user 1–3 days |
| Linear Issue tracking | Moderate | Dev 15–60 min | Any user Same day |
| Meta (Facebook, Instagram) Social media | Hard | Dev 30–90 min | Any user 2–6 weeks |
| LinkedIn Social / Professional network | Gated | Dev 30 min – 2 hours | Any user 4–12 weeks |
| YouTube Data API Video | Hard | Dev 30–90 min | Any user 3–8 weeks |
| Google Ads Advertising | Hard | Dev 1–2 hours | Any user 1–4 weeks |
| Sentry Error monitoring | Hard | Dev 30–90 min | Any user 1–6 weeks |
| Supabase Database platform | Trivial | Dev 15–60 min | Any user Same day |
| Vercel Developer platform | Moderate | Dev 1–3 hours | Any user Same day |
| Atlassian (Jira, Confluence) Project management | Moderate | Dev 30–90 min | Any user Same day–3 weeks |
| Zoom Video meetings | Hard | Dev 15–60 min | Any user 2–6 weeks |
| Asana Project management | Moderate | Dev 15–60 min | Any user Same day |
| Dropbox File storage | Moderate | Dev 15–45 min | Any user 2 days–2 weeks |
| Airtable Database | Moderate | Dev 15–60 min | Any user Same day |
| Calendly Scheduling | Moderate | Dev 15–45 min | Any user Same day |
| Shopify E-commerce | Hard | Dev 30 min–2 hours | Any user 2–6 weeks |
| Stripe Payments | Hard | Dev 1–3 hours | Any user 1–3 weeks |
| Zendesk Customer support | Hard | Dev 30–90 min | Any user 2–6 weeks |
| Intercom Customer support | Hard | Dev 30–60 min | Any user 1–3 weeks |
Use it where you work
- 1Search any app
- 2Read the verdict and the steps
- 3Let the AI draft the paperwork
How guides are made
Provider rules change often, and a wrong guide can cost weeks. So every guide says who checked it, and every claim says how we know it.
- Agent-researched (110)
- Researched by agents from official docs with cited sources and checked links. Not yet reviewed by a person.
- Live agent
- Written on request for apps not in the library, in about two minutes.
- 1
Identify. Confirm the app exists and offers OAuth to third-party developers.
- 2
Probe. Fetch the provider's live OAuth metadata. Only live probes and attempts can make a claim "tested".
- 3
Read. Find and read the provider's official developer docs and policy pages, keeping every source.
- 4
Try. Attempt the first setup steps logged out: the sign-in URL with a test app, the token endpoint, the developer console.
- 5
Dig deeper. Look at what's still unclear and decide whether a couple more targeted searches would settle it.
- 6
Audit. Check that every cited link resolves, then downgrade claims the sources don't support.
- TestedObserved directly in a setup attempt or live check
- SourcedStated in a cited source
- InferredReasoned from sources, not stated outright
- UnverifiedNot confirmed; check before relying on it
- Trivial
- Self-serve, no review
- Moderate
- Self-serve, with limits or optional review
- Hard
- Mandatory review before most users can connect
- Gated
- Useful APIs need partner approval