Connector agents

Four agents are seeded only when the connector they depend on is configured: Google Workspace, Microsoft 365, Slack Assistant and Zoom Meetings. An agent that declares a tool nobody can authenticate is worse than absent — it is misleading — so these appear when they can work, and not before.

At a glance

Google Workspace

One agent for your Google account: calendar and Google Meet meetings, Gmail, and Drive — because one request often spans them ("find the proposal Priya sent and book 30 minutes to go through it"). Meetings with other people get a Meet link, and attendees are emailed the invitation. Reading runs immediately; creating an event, sending mail and writing documents pause for your approval.

Microsoft 365

Outlook mail, your calendar with Microsoft Teams meetings, and contacts. Meetings with other people are created as Teams meetings with a join link, and attendees receive the invitation. Sending mail and creating events pause for your approval. OneDrive and SharePoint files are not available yet.

Earlier Google agents

GMail Inbox Triage and GDrive Librarian are no longer seeded: Google Workspace does both jobs. An organisation that already has them keeps them — still reachable by @handle and installable from the template gallery — but they stop being routing candidates once Google Workspace exists, so a Google request is never split between near-duplicates. A copy your organisation edited is left exactly as it is.

Which agent gets "schedule a meeting"

• Named provider wins. "Set up a Zoom call", "a Teams meeting", "a Google Meet" go to that provider's agent.
• Otherwise, your preference. Under Settings → Meetings each person switches on the providers they use and ranks them; the first one available is used. With none switched on, the assistant decides.
• Replies stay put. When an agent ends its answer with a question ("how long should it be?"), a short reply such as "1 hour" or "Approve" goes back to that agent rather than being routed afresh. A longer message is routed with that question in view, so a genuinely new request still finds its own agent.

GMail Inbox Triage

It reads your mail and tells you what actually needs you today, rather than summarising everything. Reading runs immediately; drafting, sending, labelling and trashing are writes and pause for your approval.

GDrive Librarian

It finds documents in your Drive and answers from them — useful when you know the answer is in a file but not which one. It reads through the Drive and Docs APIs under one Google consent.

Slack Assistant

It finds channels, catches you up on what was said, and posts or replies for you — as you, under your name. Listing channels and reading history run immediately; posting is a write and pauses for your approval, with the exact text and channel shown first. It reaches only channels you can see, and tells you to join one first when Slack says you are not a member.

This is the Slack connector — an agent acting in Slack. Talking to agents from Slack is the separate Slack channel, set up under Settings → Channels.

Zoom Meetings

It lists your upcoming and live meetings with their join links, lists your cloud recordings for a date range, and schedules meetings on your Zoom account in your timezone. Reading runs immediately; scheduling is a write and pauses for your approval. It does not cancel or edit meetings, and it cannot see what is inside a recording.

Turning them on

An administrator registers the connector's OAuth app with the provider and configures its client id and secret for the deployment (for Slack and Zoom, see Setting up Slack and Zoom); the agent is seeded at the next sign-in. Each person then connects their own account once, under Settings → Connectors.