Connector-Worker: Gmail and Google Sheets Actions From a Workflow Step
A new connector-worker exposes Gmail send/list and Google Sheets read/append as discoverable, auditable actions for gateway customers.
A new service, connector-worker, gives gateway customers their first set of third-party actions beyond AI completions: gmail.send, gmail.list, sheets.read, and sheets.append. It's the first piece of what's shaping up to be an OpenConnector-style layer on the platform — connect a third-party account once, then call actions against it the same way you'd call any other API.
Discovery, then execution
Two endpoints do the work: one lists which actions are available for your own active connections, the other executes one after validating its parameters against that action's declared schema. Every route resolves who's calling first and scopes every query to that identity — there's no path where a caller can reach into another customer's connection or data by passing a different ID.
A couple of details worth knowing if you're building against it: gmail.list doesn't hand back bare message IDs — it enriches each result with subject, sender, date, and a snippet, so a caller doesn't need a second round trip just to know what a message is, and it's capped at 25 results per call. sheets.append does its own extra validation on top of the standard schema check, because "an array of spreadsheet rows" isn't a shape the platform's flat field-validation format can express on its own.
Every call is logged, redacted
Each action execution writes a log row regardless of whether it succeeded — but deliberately without the action's parameters, tokens, or response body. The log answers "did this call happen and did it work," not "what exactly was sent," matching the same privacy boundary already drawn around AI completion logging elsewhere on the platform.
What it needs first
Actions only work against a connection that's already authorized — this release is the execution layer; a Google account still needs to be connected before gmail.send or sheets.append have anything to act on. That connection flow is its own piece of this rollout.
Gmail and Sheets are the first two integrations; the action registry is built to add more without reworking the discovery or execution paths.