# Google Workspace
> Calendar, Drive, Docs, Sheets, Slides, Tasks, and Contacts — connected individually, so an agent gets exactly the access it needs.
Seven Google services beyond [Gmail](/docs/connect/gmail/) are available as connectors. Each is authorized **separately**, so an agent can read your calendar without touching your files.
## When to use it
Connect the specific service the agent's job requires. Meeting prep needs Calendar and maybe Drive. A reporting agent needs Sheets. A writing agent needs Docs. Connecting all seven to every agent is the opposite of the intent.
## What each one does
| Service | An agent can | Gated |
| --- | --- | --- |
| **Calendar** | List events over a range, read one with attendees and location, create an event | — |
| **Drive** | Search, read, create, update files; delete | Delete |
| **Docs** | Create a document, read it, append, replace text; delete | Delete |
| **Sheets** | Create a spreadsheet, read a range, append rows, update cells; delete | Delete |
| **Slides** | Create a deck, read it, add a slide, replace text; delete | Delete |
| **Tasks** | List task lists and tasks, create, complete, update; delete | Delete |
| **Contacts** | Search and read contacts, create, update; delete | Delete |
Creating and updating are **not** gated — an agent can write a document or fill a sheet without interrupting you. Deleting always is.
## Connect them
Each service is its own entry in the connector list, and each sends you to Google's consent screen for that service's permissions. Bind each connection to the agents that need it.
Authorizing all seven means seven trips through consent. That friction is intentional: the alternative is one grant that covers everything you have in Google.
## Patterns that work
- **Meeting prep.** Calendar to find the meeting, Drive to find the related documents, Docs to write the brief.
- **Recurring reports.** Sheets as the data source, Docs or an [artifact](/docs/capabilities/artifacts/) as the output, a [routine](/docs/automate/routines/) to run it weekly.
- **Write to Endue first, export later.** Producing an [artifact](/docs/capabilities/artifacts/) and copying it into Docs when you are happy is often better than iterating directly in a live document.
## Limits
- Each service is authorized separately; there is no single Workspace grant.
- One Google account per connection, per service.
- An agent works with files it can find through search or a link you give it. It does not browse your whole Drive to decide what is relevant.
- Endue exposes the operations in the table above, not the full Google API — advanced formatting, permissions changes, and sharing settings are out of reach.
## Related