Documentation
OAuth connectors
Shipping in stages. Slack OAuth is fully self-serve through the dashboard's Connect apps flow today. The non-Slack connectors below (Drive, GitHub, HubSpot, Stripe, Notion, Linear, Calendar, +) are being wired up one at a time — clicking the Connect apps → [tool] button today opens an email draft to hello@getmonroe.com and we follow up within one business day to wire the OAuth credentials server-side. Self-serve OAuth install for each tool ships in upcoming releases; the scoping + revocation behavior below is the design once that flow lands.
Monroe connects to every supported tool via OAuth — no passwords ever enter the system. Each connector is scoped to what you grant.
The catalog
See /integrations for the full list with status. The most-connected on day one:
| Tool | Default scope | What Monroe can do |
|---|
|---|---|---|
| Google Drive | Folder-level | Read approved Docs/Sheets/Slides/PDFs, draft new docs, never delete |
|---|---|---|
| GitHub | Repo-level | Read PRs/issues/commits, comment with approval, never push without explicit approval |
| HubSpot | Read all, write with approval | Research accounts, draft notes, draft follow-ups |
| Stripe | Read-only by default | Summarize MRR, flag failed payments — refunds always require approval |
| Notion | Workspace + page scope | Search workspace, draft pages, never delete |
| Linear | Workspace-level | Read issues, drag-and-drop status, comment with approval |
| Google Calendar | Read + write with approval | Read schedules, prep briefs, never schedules without OK |
How scoping works
You grant Monroe access to a specific folder, repo, or workspace — not the whole account. Examples:
- "Connect Drive → grant access to /Customer/ACME/ folder only" → Monroe never sees /HR/.
- "Connect GitHub → grant access to acme/marketing repo" → Monroe doesn't see acme/infra.
- "Connect HubSpot → read-only" → Monroe drafts CRM updates as comments for your review; never updates a record directly.
Revocation
Two ways to disconnect:
1. From Monroe: Dashboard → Connect apps → click Disconnect. Monroe drops the credential and loses access on the next call.
2. From the upstream tool: GitHub/Google/etc. all have "Apps & Authorized Connections" pages. Revoke Monroe there.
Either way, Monroe loses access within seconds.
Per-connector approval rules
Different tools have different default approval requirements. See approvals for the full table. You can customize per-tool in Settings → Approvals.
Next: MCP.