Google Chat

GOOGLE WORKSPACE · MESSAGING

Read and post in the spaces that person belongs to.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

google_chat_add_memberWRITE

Add a member to a Google Chat space.

chat.memberships

google_chat_create_spaceWRITE

Create a new Google Chat space (room).

chat.spaces.create

google_chat_delete_messageWRITE

Delete a message from Google Chat.

chat.messages

google_chat_delete_spaceWRITE

Delete a Google Chat space.

chat.delete