Connected apps guide
Instinct AI integrations: Gmail, Calendar, and Google Drive
The Google apps named in Instinct's policy, the difference between a connection and a completed task, and a practical way to check account access.
Key takeaways
- Instinct's policy names seven Google Workspace services; the table below lists them.
- A named integration does not establish support for every operation in that app.
- Check account identity, permissions, and the saved result when evaluating a workflow.
- These are documentation findings and suggested checks, not account testing results.
Which apps does Instinct connect to?
Instinct's privacy policy names Gmail, Google Calendar, Google Drive, Google Docs, Google Sheets, Google Slides, and Google Tasks when you link Google Workspace. Its homepage also describes access to applications and devices, including messaging, screen, audio, and location. These are different kinds of access, not one interchangeable integration catalog.
For a useful comparison, start with the exact job you need completed. ‘Works with Google Calendar’ leaves several questions open: which calendar, which operation, whose events, and what happens when a guest declines? Treat a named service as a reason to investigate a workflow, then confirm the operation and permissions in your account.
| Named Google service | What to check for your task |
|---|---|
| Gmail | Correct account, selected conversations, and whether you are requesting a draft or a sent message. |
| Google Calendar | Calendar owner, time zone, guest list, and permission to create or change events. |
| Google Drive, Docs, Sheets, and Slides | Exact file, sharing boundary, and whether a proposed edit may be saved. |
| Google Tasks | Correct list, due date, and whether existing tasks may be changed. |
An integration and operating an app are different paths
Instinct describes an assistant trained to operate a phone and computer. That does not establish a native connector for every website or app. A product may reach information through a connected account, work through a visible interface, or need you to complete an authentication step. Ask which route applies to the particular service you need.
Keep three questions separate: can the assistant access the information, can it perform the requested operation, and can you verify completion? A login that succeeds answers only the first part. For example, a scheduling workflow also needs to handle the correct date, prevent duplicate invitations, and return a saved event you can open.
The reviewed pages do not establish support for Outlook, Slack, or a custom MCP server. Record each requirement as documented, confirmed in your account, or unanswered.
Check the permission boundary before the first task
Instinct's terms authorize access, collection, indexing, and actions through connected services. They also explain that actions can have consequences and safeguards do not guarantee an error-free result. Review the actual authorization screen alongside your intended task, rather than interpreting a connection as a narrow permission to read one item.
First check the account identity. Personal and work addresses can create different sharing expectations. Compare the requested access with the information needed for your task. If the connection requests broader permissions, establish whether those permissions are necessary and acceptable before proceeding.
A request such as ‘draft only’ states your instruction; it does not prove that sending is technically disabled. Where the product or connected service offers separate controls, inspect them. If your workflow needs a permission boundary that you cannot confirm, keep the consequential step manual.
Try one workflow with a result you can inspect
Suggested check, not a tested Instinct capability: select a non-sensitive email thread and ask for a summary of the outstanding question, its deadline, and a draft response. Identify the thread yourself and prohibit sending. This gives you a small result to compare with the original material before you delegate a larger inbox review.
For a calendar check, ask for a proposed plan around a familiar event. Inspect its date, time zone, and travel buffer before considering actual changes. Save the request, result, and corrections, and include supervision time when judging usefulness. Repeat a small check after changing accounts or permissions.
Keep a clear end to each connection
Before connecting, decide when you will revisit permission: after a trip, after a project, or when you stop using the assistant. Keep a list of accounts involved so you can distinguish active workflows from access that no longer serves a purpose.
Review both connection and deletion settings when your task ends. The privacy guide linked below explains the official destinations and why ending access should be considered separately from removing previously collected information.
This guide was checked against public documentation on September 20, 2026. We did not test a signed-in Instinct account. The table and suggested checks help you evaluate your own setup; they are not a promise that each operation is available.
Directory picks
Agents mentioned in this guide
Source notes
Primary references
We use first-party product pages and technical documentation wherever possible. Listing access can change, so check the linked source before relying on a number or feature.
Related resources