Google Workspace

Services included

Agents use Google Workspace through the Google Workspace CLI, which runs in the agent’s sandbox, so this integration needs an Internal agent (Internal agents always have a sandbox; Customer-facing agents have none).

There are two ways to connect, and they differ in what the agent can reach.

Service	Sign in with Google	Service account (Workspace admin)
Google Docs	Read and write document content	same
Google Sheets	Read and update spreadsheet cells	same
Google Slides	Create and edit presentations	same
Google Forms	Create forms and read their responses	same
Google Contacts	Look up contacts to address a message	same
Google Calendar	Read events, create events, check availability	same
Google Drive	Create and upload files. Listing or reading existing files is not available	Full read and write
Gmail	Send email. Reading, searching, replying and forwarding are not available	Read, search, triage, reply, forward

Sign in with Google is the default and takes seconds. It requests only the permissions Google classifies as non-sensitive or sensitive, which is why reading Drive and Gmail is not on the list — those need Google’s restricted permissions.

Service account is for organisations that need those. A Google Workspace administrator authorises a service account in their own Admin Console, and the agent then acts as one named Workspace user. It is behind Advanced — Workspace admin in the connect dialog.

Before choosing a service account

Domain-wide delegation is powerful and needs a deliberate decision:

• It requires a Google Workspace administrator. Personal @gmail.com accounts cannot use it.
• The agent acts as one licensed user account. Google Groups and email aliases cannot be used — so a shared support@ address that is a Group will not work.
• The permissions are set in your Admin Console, not by Auteryn, and you can revoke them there at any time by deleting that row. It takes effect immediately.

Auteryn shows you the exact permission list to authorise and asks you to confirm the user address before accepting the key.

Calendar is a separate connection

Google Calendar is also available as its own connection (Console → Integrations → Google Calendar). An Internal agent works with your calendars through the Google Workspace CLI in its sandbox, as in the table above. The Google Calendar connection is how a Customer-facing agent, which has no sandbox, lists events and creates an event. A new or updated event can also start a Loop on an Internal agent. To receive customer email, use the Email channel (Console → Integrations → Email): forward your support inbox to the Auteryn address it gives you.

---

Connecting Google Workspace

1. Go to Console → Integrations → Google Workspace
2. Click Connect Google Workspace
3. Choose the Google services this connection may use (all are selected by default) and click Connect
4. Choose which Google account to connect
5. Grant the permissions requested and click Allow

The agent using this connection must be an Internal agent: the Google Workspace CLI runs inside its sandbox.

Personal vs. service account

A personal Google connection acts as you. On a team, it is shared with your team unless you choose otherwise when you connect. If you choose Only you or Specific people, teammates must be granted access before they can use it. It’s revoked if you leave the organization. A service account is shared with the whole team and stays durable no matter who comes or goes. For shared team deployments, connect using a Google service account rather than a personal account.

Connect with a service account (admins)

For org-wide automation, connect Workspace as a service account with domain-wide delegation instead of a personal sign-in:

1. In Google Cloud, create a dedicated service account and download its JSON key
2. In the connect dialog, open Advanced — Workspace admin and click Use a service account. Auteryn lists the exact scopes to authorise
3. In your Admin Console (Security → API controls → Domain-wide delegation), authorise the service account’s client ID for only those scopes
4. Back in Auteryn, enter the Workspace user to act as (e.g. automation@yourcompany.com), retype it to confirm, and paste the JSON key
5. Click Connect and test. Auteryn runs a live test, so you find out at once whether the authorisation worked rather than when an agent first tries to use it

The connection is labeled Team account: one org-constant identity, no per-person credentials, unaffected by anyone leaving.

---

Example tasks

Google Drive / Docs

• “Create a new Google Doc titled ‘Meeting Notes - April 1’ with the following content…”
• “Save this report as a file in my Drive”

Google Sheets

• “Read the data from Sheet 1 of the ‘Sales Tracker’ spreadsheet”
• “Update cell B5 in ‘Budget 2025’ to 45000”

Google Calendar

• “What meetings do I have tomorrow?”
• “Create a 30-minute meeting called ‘Sprint Planning’ on Friday at 2pm for me and alice@acme.com”
• “Find a free slot this week for a 1-hour meeting with alice@acme.com”