Comms
Gmail
Read and send email, as part of Google Workspace.
Official site: mail.google.com
What it does
- Search threads and read messages
- Create drafts and send email
Composing defaults to sending, not drafting — worth knowing precisely because it's easy to get backwards. Omitting the mode on a compose call sends immediately rather than leaving a draft for review, so anything meant to sit for a human to check first needs draft mode passed explicitly, every time.
Why through Tulina
Most systems now publish their own way for a model to reach them, and that is a good thing — it is what Tulina connects to. The connection was never the hard part. Deciding who may use it, what it is allowed to return, and what the model knows before it asks: that is.
The keys stay in one place
Connect Gmail 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 is handed more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
Roles decide who can reach Gmail at all. Beyond that, a policy on the connector itself decides what comes back: fields dropped, identifiers masked or hashed, people pseudonymised. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
Runs are logged for the organisation — what was called, by whom, when. That is what makes an automated action reviewable after the fact, and what a security review asks for first.
The run starts knowing your company
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 Gmail returns something usable instead of something generic.
Processes that run on Gmail
Draft the monthly investor update
Revenue, pipeline, the plan's own targets, and last month's commitments are pulled together into a draft with the numbers already in it.
Draft the quarterly LP letter
Portfolio metrics gathered from founder updates and dashboards, drafted into your quarterly letter, with every figure carrying the date it was reported.
Find local points of sale
Every target city gets searched three different ways for shops that fit your positioning, each one ranked before you ever send an email.
Keep your knowledge base current
Every morning, the previous day's activity gets read across your team's tools and synthesized into what changed, automatically and unattended.
Re-engage quiet accounts
Quiet paying accounts get one relevant note each, grounded in what they said last, with the outreach date stamped back so nobody's emailed twice.
Revive deals that went cold
Deals lost more than 90 days ago come back with fresh signals, contacts checked for job moves, and the features they asked for that have since shipped.