Integrations
Connect the tools you work with
GmailSearch and read messages with separately granted Gmail access.
Google DriveFind files, inspect metadata, read supported Docs, and create folders.
Google CalendarExplore calendars and events, then create events when permitted.
ClickUpSearch workspace tasks, inspect project structure, and create tasks.
GitHubRead private repositories and perform explicitly requested repository writes.
Google AnalyticsRead GA4 properties, traffic reports and realtime visitors.
Search ConsoleRead search performance, sitemaps and URL index status.
NotionSearch and read Notion pages and databases, then create pages, text and comments.
SlackRead channels, messages, threads and members, then send a message with approval.Planned, not yet available
More tools, after verification.
Planned integrations do not have public capability pages until they are implemented and verified for release.
Reads, writes and reporting delays at a glance
Every connector below is scoped to a short list of operations rather than blanket account access. Reads can run under Allow; anything that writes can stay on Ask and produce an approval ticket naming the exact target first. The table is generated from the same capability data as the detail pages, so it cannot drift from what the extension actually offers.
| Service | Operations | Writes available | Stated limits |
|---|---|---|---|
| Gmail | 3 | Read only | 3 |
| Google Drive | 4 | Yes, with approval | 3 |
| Google Calendar | 4 | Yes, with approval | 3 |
| ClickUp | 4 | Yes, with approval | 3 |
| GitHub | 3 | Yes, with approval | 3 |
| Google Analytics | 3 | Read only | 3 |
| Search Console | 4 | Read only | 3 |
| Notion | 4 | Yes, with approval | 3 |
| Slack | 4 | Yes, with approval | 3 |
Beyond the released list: custom connectors and MCP
When a service is not on the list, two routes exist without waiting for a release. A custom HTTPS connector is described with an OpenAPI 3 document, and credentials are stored server side and encrypted rather than kept in the browser. A remote MCP server can be registered the same way, with its tools validated per operation. Both routes inherit the same Allow, Ask and Deny policies and the same approval tickets as the built in connectors, and outbound requests are checked to block requests aimed at private network addresses.
Data freshness and access, stated up front
- Search Console reporting commonly lags by 2 to 3 days. A report for “yesterday” is not a complete day.
- GA4 standard reports can stay incomplete for roughly 24 to 48 hours; realtime metrics are a separate, narrower read.
- Notion only exposes the pages and databases you shared with the connection during authorization.
- Slack only sees channels the connected app can access; private channels require an invite, which is itself an approved step.
- GitHub uses the provider repo scope, which is broad by design at the provider level, so consequential writes are best left on Ask.
- An empty result is reported as possible missing access rather than as proof that nothing exists.