CommsConnector
Google Workspace
Read and send Gmail, manage Calendar events, and read and write Sheets and Drive files, from Claude or ChatGPT, through Tulina's MCP server.
Official site: workspace.google.com
What it can do
1 write/2 send
- 01Send
Read and send Gmail, and manage Calendar events
- 02Write
Read and write Sheets and Drive files
- 03Send
Read and post in Google Chat
Each person authorises their own account — nothing here runs on a shared, org-wide credential. Sending or reading on someone's behalf is easy to over-scope; the right default is exactly what the task needs, no more.
How do you connect Google Workspace to Claude and ChatGPT?
Through Tulina's own MCP server, not Google's own hosted Workspace MCP servers. Read and send Gmail, manage Calendar events, read and write Sheets and Drive files, or post in Google Chat, each under the account that person authorized, in the same chat as the task it's for, whether that chat is Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Google Workspace once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Google Workspace at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Google Workspace returns something usable instead of something generic.
Processes that run on Google Workspace
None published yet.