Waydock connects your accounts once and turns everything they hold into one unified context. This page covers what you can connect, how each is authenticated, and how data flows in.
For agents: call
waydock_capabilities(no scope required) to see which providers a given key's owner has connected. Read scopes gate what you can pull from each.
What you can connect
| Provider | Brings in | Auth | Agent can |
|---|---|---|---|
| Gmail | Mail and calendar | OAuth | Read, draft, send |
| Outlook / Microsoft 365 | Mail and calendar | OAuth | Read, draft, send |
| Microsoft Teams | Chats and messages | OAuth | Read, and send with a separate scope |
| Fathom | Meeting recordings, transcripts, summaries, action items | OAuth or API key | Read |
| Fireflies | Transcripts, summaries, action items | API key + webhook | Read |
| Recordings, transcripts, mind maps, action items | API key + webhook | Read | |
| Linear | Issues | OAuth | Read, and create issues |
| Jira | Issues | OAuth | Read, and create issues |
| WHOOP | Recovery, sleep, strain | OAuth | Read (personal workspace only) |
You can connect multiple accounts per provider. Each is an independent source with its own sync.
Connecting an account
- Go to Settings → Connections.
- Pick a provider.
- OAuth providers (Google, Outlook, Teams, Linear, Jira, WHOOP, Fathom) redirect you to the provider to grant access. Waydock requests least-privilege scopes, and you can disable drafting or sending per account afterward without reconnecting.
- API-key providers (Fireflies, Pocket, and Fathom by key) take a key you paste, plus an optional webhook secret. Waydock returns the webhook URL to register with the provider.
- Waydock backfills recent items and starts syncing.
You can also add an account from a second device with a one-time pairing link generated in Settings → Account → Connect from another device.
How data flows in
Waydock uses push where a provider supports it, and polling as a backstop.
- Gmail streams changes over Google Pub/Sub, with a delta poll as backup.
- Outlook and Teams use Microsoft Graph change notifications, with a reconciliation poll.
- Fathom, Fireflies, and Pocket send signed webhooks when a meeting is ready, verified and deduplicated on arrival.
- Linear and Jira are polled.
- WHOOP is fetched on demand.
Sync cadence follows your plan: hourly on Free, as often as every 5 minutes on Pro (mail providers apply their own floor, so the realized interval can be longer). Every sync records a log you can see under Settings → Activity, showing the last run, its status, and how many items it pulled.
Cards, the common shape
Everything that syncs becomes a card: an email, a calendar event, a meeting, a task, or a Teams message, all with a shared shape (source, title, summary, status). Cards are what your daily surfaces and your agents read, so an agent can reason across sources instead of one silo.
Historical mail backfill
By default Waydock reads recent mail live and indexes a rolling window. To pull older mail (for example, a full quarter), Pro users can run a Direct Source Fetch: a consent-pinned backfill where you approve a date range and filters, and Waydock fetches that mail into your archive under the approved bounds. Every backfill is logged.
Privacy defaults
- Waydock reads your mail live at query time and never trains on your data.
- Storing full email bodies, meeting transcripts, or Teams message bodies at rest is an opt-in, off by default, and encrypted when enabled. Without it, Waydock keeps metadata and snippets.
- Provider tokens and webhook secrets are always encrypted at rest.
Where to go next
- Quickstart to connect an agent to your context
- Tool reference for the tools each provider unlocks
- Security for how connections and sends are governed