Connections
Link your calendar, email, and other services so your assistant can act on your behalf.
What connections are
A connection gives your assistant access to an external service under your identity. Without connections, your assistant can have a conversation and create tasks — but it can't read your calendar, send email, or interact with any service on your behalf.
Connections are personal: each user connects their own accounts. They're managed under Connections in your settings.
Connecting Google gives your assistant access to your Google Workspace services. You can connect each independently:
Google Calendar — your assistant can read your availability, create and update events, and participate in scheduling coordination. This is the most fundamental connection: without it, your assistant can't book anything on your behalf.
Gmail — your assistant can search and read your inbox, and (with read/write permission) send emails, archive messages, add labels, and save drafts. When Gmail is connected, outbound emails from your assistant come from your actual Gmail address rather than your assistant's default address.
Google Drive — your assistant can access and attach files from your Drive. Tasks that involve documents or files can pull from Drive directly.
Microsoft
Connecting Microsoft gives your assistant access to your Microsoft 365 services:
Outlook Calendar — same as Google Calendar: availability, event creation, and scheduling.
Outlook Mail — search, read, and send via your Outlook address. With read/write permission, your assistant can also archive, flag, and organize your inbox.
OneDrive — file access and attachments from OneDrive.
Slack and Microsoft Teams
Unlike the connections above, Slack and Teams aren't something you personally connect — your company's workspace is connected once, for everyone, by an org admin or IT. See Slack & Teams for how that works and what it looks like once it's set up. If you try to message your assistant there and nothing happens, your workspace probably just hasn't been connected yet — ask your admin.
Permission levels
Calendar and file connections are read/write by default — your assistant needs write access to create events and upload files.
Email connections have two levels:
| Level | What your assistant can do |
|---|---|
| Read | Search inbox, read emails, list threads — no sending or modifying |
| Read/write | Everything in read, plus send emails, archive, label, draft, move to trash |
Your org admin may have set a policy on which level is available. If you only see read access, contact your admin.
What happens if a connection breaks
OAuth tokens expire or get revoked when you change your account password, revoke app access in your provider settings, or your token reaches its expiration. When this happens:
- Your assistant loses access to that service immediately
- You'll see a notification in your inbox with a "Reconnect" action
- Tasks that depend on the connection will pause or fail until you reconnect
To reconnect, click the notification in your inbox, or go to Connections and re-authorize the affected service.
Connections for skills
Some skills require their own connections — for example, a Salesforce skill needs your Salesforce credentials. These are managed separately from your calendar and email connections, usually via an API key you paste in when installing the skill. The skill's store page will tell you exactly what it needs before you install.