Integrations / Work from your existing systems

Your tools. Connected to the work.

Crew One works from the systems your company already runs on. Connect the tools the work needs, with the access you grant.

Not all connections work the same way

01 / The connections

What each connection does.

Capabilities and limits, side by side. These are integrations, not customer endorsements.

Gmail
Reads and triages your inbox, drafts replies, and sends once you approve.
Google OAuthSend after approval
Google Calendar
Reads your schedule, finds free time, and books events you approve.
Google OAuthApproved bookings
Google Drive
Finds and reads the documents your crews need for context.
Google OAuthRead access only
Linear
Reads project context, and files or updates issues you approve.
OAuthApproved issue changes
Notion
Searches and reads your pages, and writes back the context worth keeping.
OAuthRead and write
Slack
Reads channels, answers where the work happens, and delivers your briefing.
OAuthTeam communication
Stripe
Pulls live MRR and ARR into your metrics.
Stripe ConnectRevenue metrics only
WhatsApp
A surface you talk to Crew One on, with the same memory as the web app.
Meta Cloud APIA channel, not a data source

02 / How access works

You connect it
Google, Slack, Notion and Linear connect over OAuth. You authorise each one from your own account.
Context stays traceable
Crews pull what they need to do the work, and cite the source they took it from.
You set the rules
You set the approval rules for money, external messages and company data.

Stripe uses Stripe Connect. WhatsApp uses Meta Cloud API credentials. Neither follows the per-user OAuth flow above.

Explore the example workspace, or apply for access to Crew One.