Google Workspace

• Write filesfile.writeDry run

  Files a generated report or export into Drive, or updates one already there.

  Reads: rootFoldersharedDriveRaises: google.file.createdgoogle.file.updated
• Read filesfile.readDry run

  Lists files in scope with their type, owner, size and last modification.

  Reads: domainsharedDriverootFolderRaises: nothing
• Append to sheetssheet.appendDry run

  Adds rows to a tracking sheet. Cannot overwrite, which is why Memory binds to it.

  Reads: rootFoldersharedDriveRaises: google.sheet.appended
• Synchronise foldersstorage.syncDry run

  Reconciles a knowledge folder in both directions and reports what moved each way.

  Reads: rootFoldersharedDrivesyncFrequencyRaises: google.folder.synchronisedgoogle.sync.completed
• Search filesfile.searchDry run

  Queries across the drive by name, type or content. The Knowledge Graph's route in.

  Reads: domainsharedDriverootFolderRaises: nothing
• Read foldersfolder.readDry run

  The folder tree beneath the configured root, with depth and child counts.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write foldersfolder.writeDry run

  Creates or moves a folder so filed output has somewhere to land.

  Reads: rootFoldersharedDriveRaises: google.file.created
• Read permissionspermission.readDry run

  Who can reach each file in scope, by what role, and how they were granted it.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write permissionspermission.writeDry run

  Grants or revokes access to a file or folder as a workflow or compliance action.

  Reads: domainrootFolderRaises: google.permission.grantedgoogle.permission.revoked
• Read revisionsrevision.readDry run

  Revision history and authorship — the provenance behind an audited document.

  Reads: domainsharedDriverootFolderRaises: nothing
• Read documentsdoc.readDry run

  Structured Docs content: body, headings and tables, rather than the file's bytes.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write documentsdoc.writeDry run

  Creates a document, inserts into one, or publishes it to the estate.

  Reads: rootFoldersharedDriveRaises: google.file.createdgoogle.document.published
• Read spreadsheetssheet.readDry run

  Ranges and their values, for the figures the Intelligence Center reads rather than writes.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write spreadsheetssheet.writeDry run

  Updates a named range in place, as distinct from appending to the end.

  Reads: rootFoldersharedDriveRaises: google.file.updated
• Read presentationsslide.readDry run

  Slides and their speaker notes, for briefing material an executive already has.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write presentationsslide.writeDry run

  Builds or updates a deck from a report the platform generated.

  Reads: rootFoldersharedDriveRaises: google.file.created
• Read commentscomment.readDry run

  Open comment threads across the selection — the human review trail on filed work.

  Reads: domainsharedDriverootFolderRaises: nothing
• Write commentscomment.writeDry run

  Replies to or resolves a comment thread as the acting agent.

  Reads: rootFolderRaises: google.comment.added
• Read mailmail.readDry run

  Threads in the delegated mailboxes, for triage into the Communication Hub.

  Reads: domainRaises: nothing
• Send mailmail.sendDry run

  Sends an addressed, threaded message from a delegated mailbox.

  Reads: domainRaises: google.mail.sent
• Draft mailmail.draftDry run

  Stages a message for a human to approve. Raises nothing, because nothing was sent.

  Reads: domainRaises: nothing
• Read calendarcalendar.readDry run

  Events, attendees and free/busy across the delegated calendars.

  Reads: domaintimezoneRaises: nothing
• Write calendarcalendar.writeDry run

  Creates, moves or cancels an event in the configured timezone, with a Meet link.

  Reads: domaintimezoneRaises: google.calendar.event.createdgoogle.calendar.event.updatedgoogle.calendar.event.cancelled
• Read directorydirectory.readDry run

  Workspace users and groups. Not the Communication Hub's own internal directory.

  Reads: domainRaises: nothing
• Read contactscontact.readDry run

  The address book, including people outside the domain. Not the admin directory.

  Reads: domainRaises: nothing
• Write contactscontact.writeDry run

  Adds or amends an address book record, including people outside the domain.

  Reads: domainRaises: google.contact.added
• Read meetingsmeet.readDry run

  Conference spaces with their attendance and recordings, separate from the calendar entry.

  Reads: domaintimezoneRaises: nothing
• Write meetingsmeet.writeDry run

  Provisions a conference space, or marks one live. Separate from the calendar entry.

  Reads: domaintimezoneRaises: google.meet.scheduledgoogle.meet.started

Inbound deliveries and outbound operations both raise these onto the internal bus. The Hub is the emitter — an external platform cannot reach the bus, which is what stops it raising arbitrary internal events.

• File Createdgoogle.file.created

  A file appeared in scope, filed by an agent through the gateway or by a human in Drive.

• File Updatedgoogle.file.updated

  Existing content changed. The projected entity backing it is stale from this point.

• File Deletedgoogle.file.deleted

  Inbound only — no capability on this connector deletes. A projected node has lost its source.

• Folder Synchronisedgoogle.folder.synchronised

  A reconciliation completed. Carries what moved each way, which is the only way to tell a no-op from a failure.

• Permission Grantedgoogle.permission.granted

  Someone gained access to filed output. The single most audit-relevant event this connector raises.

• Permission Revokedgoogle.permission.revoked

  Access was removed. Separate from the grant precisely so an auditor cannot read one as the other.

• Comment Addedgoogle.comment.added

  A human commented on filed work. The route from a document back into the Communication Hub.

• Document Publishedgoogle.document.published

  A document reached a state the estate is meant to read. Distinct from merely being created.

• Sheet Appendedgoogle.sheet.appended

  Rows landed on a tracking sheet. Not the same fact as `memory.written`, which is what the platform did.

• Mail Receivedgoogle.mail.received

  Inbound only. A thread arrived in a delegated mailbox and is a candidate for triage.

• Mail Sentgoogle.mail.sent

  Correspondence left the estate. Raised by `mail.send` and never by `mail.draft`.

• Calendar Event Createdgoogle.calendar.event.created

  Time was booked in somebody's day — the one thing this connector does that a human feels immediately.

• Calendar Event Cancelledgoogle.calendar.event.cancelled

  A booking was withdrawn. Separate from creation so a reconciler cannot take the wrong action.

• Calendar Event Updatedgoogle.calendar.event.updated

  An existing booking moved. Distinct from creation: the commitment was already known, only its time changed.

• Sync Completedgoogle.sync.completed

  The reconciliation cycle finished. Estate-scoped, where `folder.synchronised` is one folder — this is what a workflow waits on.

• Meeting Scheduledgoogle.meet.scheduled

  A conference space was provisioned. Separate from the calendar entry, which may not exist.

• Meeting Startedgoogle.meet.started

  A space went live. The moment anything that must attend has something to join.

• Contact Addedgoogle.contact.added

  The address book gained a record, frequently for somebody outside the domain.

• Authentication Refreshedgoogle.auth.refreshed

  Inbound only. The plugin holds no credential and cannot refresh one — the host's auth framework raises this.

Routed by the event bus alongside the platform's own topics. See the fan-out chains.

What a future workflow step can request. Several share one capability — the capability is what the gateway routes on, the action is what an operator building a workflow recognises.

• File Reportfile.write

  Writes a generated report into the configured root. The completion step of most reporting workflows.

• Create Documentdoc.write

  Opens a structured document — a brief, a spec or a post-mortem — from a workflow's own output.

• Build Deckslide.write

  Turns a report into a presentation for a review the executive bench is holding.

• Append Rowsheet.append

  Adds a tracking row. Cannot overwrite, which is why an audit trail is bound to it rather than to sheet.write.

• Reconcile Folderstorage.sync

  Runs a two-way sync of a knowledge folder and reports what moved each way.

• Grant Accesspermission.write

  Gives a named principal a role on filed output — an onboarding step, and a reviewable one.

• Send Mailmail.send

  Sends addressed correspondence. Chosen over a chat broadcast when a durable record is the point.

• Stage Mail For Approvalmail.draft

  Writes the message and stops. The action a gated step uses when a human must clear the send.

• Schedule Meetingcalendar.write

  Books time with a conferencing link, in the connector's configured timezone.

• Generate Spreadsheetsheet.write

  Builds a sheet and writes ranges into it. `sheet.write` had no action at all until this, which made a served capability unreachable from a workflow.

• Create Meeting Spacemeet.write

  Provisions a conference space on its own, for a meeting that has no calendar entry or does not want one yet.

• Update Contactcontact.write

  Files a person into the address book. The step a sales or success workflow runs after a first exchange.

Node kinds this connector would project. External entities enter the graph on exactly the terms internal ones do — the graph owns neither, and no database change is implied by any of it.

• Shared Driveroot nodefolder.read

  The root external entity for this connector. Every folder and file hangs off one.

• Folderchild of shared-drivefolder.read

  Carries the tree structure. The one entity here whose shape is the information.

• Documentchild of folderdoc.read

  Structured content rather than a blob — links to the report or memory record it backs.

• Spreadsheetchild of foldersheet.read

  Projected as a node, never as rows. A node per row would swamp every internal entity combined.

• Presentationchild of folderslide.read

  Briefing material. Links to the review it was built for.

• Personroot nodedirectory.read

  A root, not a child of a drive. Very likely the same human GitHub projects as a developer — resolving that is the graph's decision, not this connector's.

• Meetingroot nodecalendar.read

  A root because a meeting spans people and departments. The only time-anchored entity either connector projects.

• Filechild of folderfile.read

  The generic node the three typed ones do not cover — an image, an archive, a PDF nobody will parse. Without it a folder's contents are partly invisible.

• Emailroot nodemail.read

  A root, because a thread spans people and departments the way a meeting does. Projected as a thread, never as a message — one node per message would swamp the graph exactly as spreadsheet rows would.

• Contactroot nodecontact.read

  A THIRD person-shaped root, beside `person` here and `developer` on GitHub, and frequently somebody outside the domain that neither of those can see. Reconciling the three remains the graph's decision, not this connector's.

• Shared Resourcechild of shared-drivepermission.read

  A grant reified as a node: who reached what, and how. An edge would be the obvious modelling and is wrong — a grant has its own lifetime, its own author and its own expiry.

Advisory reads this connector's data would support. The Decision Engine sees one instant and stores no history, so each insight states whether it is instantaneous or needs a series.

• Output shared outside the domainpermission.read · directory.read

  Grants whose principal is not a directory member. The clearest single compliance signal this connector can produce.

• Knowledge base going stalefile.read · revision.read

  Folders whose most recent revision is far older than the department's activity would predict.

• Filed output nobody openedfile.read · comment.read

  Reports written by the platform with no comment and no revision by a human. Work that cost something and reached no one.

• Folder reconciliation divergingfolder.read · file.read

  A knowledge folder whose two sides disagree, which is the failure a scheduled sync hides best.

• Executive calendar saturatedcalendar.read · directory.read

  Booked time against available time per member. The input to whether an approval gate will actually clear this week.

• Unanswered correspondencemail.read

  Threads in delegated mailboxes with no reply. The external mirror of the Communication Hub's own escalation rule.

• Correspondence response timemail.read

  Age of the oldest unanswered thread, and the spread beneath it. Instantaneous despite sounding temporal — the ages are readable from one snapshot of open threads, where 'response time is worsening' would not be.

• File collaboration concentrationpermission.read · comment.read

  Whether filed output is reaching a working group or one person. Grants and comment authors on the same artefacts, counted distinctly.

Figures this connector would publish to the Intelligence Center. Each names the capability that supplies it, so a metric cannot be charted for a grant that does not cover the read behind it.

• Artefacts filedfilesfile.read

  Output the platform produced and stored. The closest thing this estate has to a unit of work delivered.

• Storage consumedGBfile.read

  Pooled quota drawn down. The figure that turns into a bill.

• Documents publisheddocumentsdoc.read

  Documents that reached a readable state, as distinct from merely existing.

• Reconciliation throughputfiles per cyclefolder.read

  How much a sync cycle actually moves. Falling throughput with rising duration is the shape of a failing connector.

• External grants% of grantspermission.read

  Share of access granted outside the domain. A compliance figure rather than a performance one.

• Time to first commenthourscomment.read

  How long filed output waits before a human engages with it.

• Correspondence sentmessagesmail.read

  Outbound volume from delegated mailboxes, for the Communication Hub's external reach.

• Meeting hours bookedhourscalendar.read

  Time the platform placed into human calendars. The cost side of every scheduling decision it makes.

• Correspondence receivedmessagesmail.read

  Inbound volume, beside `mail-volume`'s outbound. The two are one ratio, and a ratio nobody can compute from one half of it.

• Spreadsheets createdspreadsheetssheet.read

  New sheets rather than rows appended. Distinguishes the estate building new instrumentation from it feeding what already exists.

• Meetings scheduledmeetingscalendar.read

  A count, where `meeting-hours` is a duration. Twenty half-hours and five two-hours are the same hours and very different weeks.

• Shared filesfilespermission.read

  Artefacts with at least one grant beyond their owner. A count, where `external-grants` is a percentage — the denominator hides how much is actually moving.

Shapes of agent this connector was built for, and the capabilities each requests. Never a connector key — an agent that could name a connector could import one, and the Fleet's isolation would be a convention rather than a structure.

• Report Writerdoc.write · file.write · sheet.read · slide.write

  Turns platform output into documents and decks a human will actually open. The heaviest consumer of the write capabilities.

• Knowledge Archiviststorage.sync · folder.read · folder.write · file.search

  Owns the folder tree: reconciles it, keeps it navigable, and is the reason the Memory System has somewhere durable to write.

• Executive Assistantcalendar.read · calendar.write · mail.draft · directory.read

  Schedules and drafts. Deliberately holds mail.draft and not mail.send — nothing it writes leaves without a human clearing it.

• Correspondence Agentmail.read · mail.send

  Triages inbound threads and answers the ones it is authorised to. The one archetype here that can send unattended.

• Data Analystsheet.read · sheet.write · sheet.append · file.search

  Reads the figures the estate keeps in spreadsheets and writes derived ones back. Never touches documents.

• Compliance Auditorpermission.read · revision.read · directory.read · comment.read

  Read-only by design — advisory, like the Decision Engine. It reports who can reach what; revoking is a gated action a human clears.

• Onboarding Agentpermission.write · folder.write · directory.read · comment.write

  Provisions a new member's access and workspace. The only archetype that writes permissions, which is why it is worth naming separately.

• Schedulercalendar.read · calendar.write · meet.write · directory.read

  Split out of the Executive Assistant once Meet became its own capability. It books and provisions conferencing but holds no mail capability at all — an agent that can fill a calendar should not also be able to write to anyone about it.

• Research Assistantfile.search · doc.read · sheet.read · comment.read

  Wholly read-only, and the only archetype here that is. It finds and reads what the estate already knows; anything it concludes is written by something else.

• Sales Assistantcontact.read · contact.write · mail.draft · calendar.write

  The first archetype whose subject is routinely OUTSIDE the domain, which is why it takes contacts rather than the directory. Drafts rather than sends, for the Executive Assistant's reason.

• Operations Coordinatorfolder.write · storage.sync · sheet.append · permission.write

  Runs the recurring estate work — reconciles, files, records, grants. Distinct from the Knowledge Archivist, which owns the tree's shape rather than the traffic through it.

• Customer Success Agentcontact.read · mail.read · mail.draft · calendar.read

  Reads the relationship — correspondence, contacts and commitments — and drafts against it. Reads calendar without writing it: it can see whether an account has been neglected, and cannot book time to fix that unattended.

Archetypes, not roster entries. The Agent Fleet's own registry is unchanged by this connector existing.