AIRTECHSUPPORT OSFor Workspace admins →
google workspace developermarketplace listing · review pending

A WORKSPACE-NATIVE
AI WORKFORCE
FOR AVIATION
MAINTENANCE.

AirTech Support OS connects seven specialist coworkers and four shared sub-agents directly to Gmail, Drive, Sheets, Docs, Calendar, Forms, and NotebookLM — under your organisation's OAuth consent, with a per-role permission matrix, and a full audit trail in your existing Workspace admin console.

See the integration surface →Review permission scopes← Product overview
OAUTH SCOPES
9
minimum required
DATA EGRESS
0
stays in your Workspace
GMAIL SEND
off
draft-only by default
AUDIT TRAIL
full
every API call
01 · integration surface

FOUR SPECIALISTS.
SEVEN GOOGLE SURFACES.

Each specialist owns one Google product end-to-end and exposes a tight, role-scoped tool surface to the six primary agents. No cross-tool leakage; no general-purpose access tokens.

specialist
GmailDriveSheetsDocs

Workspace Specialist

Produces every email draft, Doc, Sheet row, and reads from Drive across the platform. Gmail is DRAFT-only — never auto-sends.

oauth scopes used
  • gmail.compose— create drafts in [email protected]/Drafts
  • drive.readonly— read institutional docs (SBs, ADs, AMM)
  • spreadsheets— read + append rows in the ops workbook
  • documents— create + update Google Docs
example operator prompts
  • Draft an MEL deferral memo as a Google Doc
  • Append a TLB row to the cases sheet
  • Email a post-holder briefing (draft for review)
  • Read the maintenance manual section from Drive
specialist
Calendar

Calendar Specialist

Schedules expiry deadlines, hangar slots, and post-holder briefings into the team calendar.

oauth scopes used
  • calendar.events— create + update events on the team calendar
example operator prompts
  • Book a hangar slot for the upcoming A-check
  • Add the MEL 49-11 deferral expiry as a calendar event
  • Schedule a post-holder briefing 24h before the dispatch decision
specialist
Forms

Forms Specialist

Generates inspection checklists, audit forms, and training quizzes — responses auto-route into Sheets.

oauth scopes used
  • forms.body— create + edit Google Forms
  • forms.responses.readonly— read response data into reports
example operator prompts
  • Create the turnaround inspection checklist for B737-NG
  • Build a CAMO audit questionnaire for an upcoming review
  • Publish a recurrent-training quiz to engineers
specialist
NotebookLM

NotebookLM Specialist

RAG search across your institutional Drive corpus — SBs, ADs, AMM revisions, technical bulletins.

oauth scopes used
  • drive.readonly— index a curated subset of institutional docs
example operator prompts
  • Find every reference to ATA 29-11 across our SBs and ADs
  • Surface the latest AMM revision affecting EC-FTR's APU
  • Cross-reference a fault code with three years of in-house TLB history
02 · permission matrix

EACH AGENT,
ITS OWN LANE.

The specialist enforces what each calling agent can request, server-side. Cortana cannot draft email; Master Chief cannot write Sheets. Audit-trail-grade.

AgentRolePermitted operationsCanCannot
CortanaTechniciandrive_list · drive_download · sheets_readreaddraft emailwrite sheetscreate docs
MorpheusMCC + TLBdrive_list/download · sheets_read/append · docs_create/update · gmail_draftreadwrite Sheetscreate Docsdraft Gmailsend emaildelete from Drive
Master ChiefExecutivedrive_list/download · sheets_read · docs_create/update · gmail_draftreadcreate Docsdraft Gmailwrite Sheetssend email
MOSSPlanningdrive_list/download · sheets_read/append · docs_create/update · gmail_draftreadwrite Sheetscreate Docsdraft Gmailsend email
HashiefQuality / CAMOdrive_list/download · sheets_read/append · docs_create/update · gmail_draftreadwrite Sheetscreate Docsdraft Gmailsend email

Enforcement is server-side at the specialist boundary — not client-side hints. A misrouted call returns a structured refusal that propagates back to the calling agent for the operator to see.

03 · privacy posture

WHAT CROSSES
YOUR ORG BOUNDARY.

Aviation compliance auditors and Workspace administrators ask the same question: what data leaves my organisation? Short answer: none of the artefact content. Long answer below.

Data stays in your Workspace

Every artefact the AI workforce produces — Gmail drafts, Google Docs, Sheets rows, Calendar events — lives in the customer's own Google Workspace, under the customer's OAuth consent. AirTech Support OS does not store copies. We hold short-lived summary strings (≤ 280 chars per case) on our infrastructure for the dashboard's audit timeline; full artefact content stays on Google.

Gmail is draft-only by default

The platform's GMAIL_SEND_ENABLED flag is off. Every email an agent produces lands in the customer's Drafts folder for human review. The operator clicks Send. There is no auto-send path in the product, and the toolWorkflow node has no gmail.send scope provisioned.

Per-role server-side enforcement

The Workspace Specialist enforces permissions in code, not in prompts. A misrouted call (e.g. Cortana asking for a Gmail draft) returns a structured refusal at the specialist boundary. No LLM judgment involved.

Full audit trail in n8n + your Workspace admin

Every Google API call is logged twice: in AirTech's n8n execution registry (workflow id, timestamp, calling agent, parameters) and in your Workspace audit log (the standard Google one your security team already monitors). Two independent records, both retrievable.

for workspace administrators

One-time OAuth admin consent installs the four specialists across the org. Revocation is a single click in admin.google.com → Security → API Controls → App access control. There is no secondary tokens store and no shadow access path.

Read the privacy policy →Request a security review call
04 · compliance posture

REGULATOR-FRIENDLY
BY CONSTRUCTION.

Aviation maintenance is one of the most heavily-regulated verticals in industry. Workspace's native compliance posture (FedRAMP · HIPAA · SOC 2 · ISO 27001) exceeds what most aviation MROs hold in-house. Building on Workspace inherits that posture for free.

  • EASA Part-145 audit-trail requirements satisfied via the dual log (n8n + Workspace admin)
  • FAA FAR 121 record-keeping satisfied via case_reference cross-linking
  • Every TLB entry written by an agent carries the calling_agent identity for accountability
  • Closure synthesis (Master Chief on case_close) lands as a Google Doc with revision history
  • MEL deferral expiries get calendar events — auditable timeline of compliance with deferred-defect rules
featured customer programme

Apply to be Google's featured aviation customer.

We are submitting AirTech Support OS to the Google Cloud customer-story programme. The first three MROs onboard with AirTech + Google Suite Plus will be invited to participate as co-named customer references — published case study on cloud.google.com, joint webinar slot, and Google Cloud Next speaking opportunity.

  • Co-authored case study (~1500 words) on cloud.google.com/customers
  • Joint Google + AirTech webinar slot (~250-500 attendees)
  • Google Cloud Next conference speaking proposal
  • Discounted first 6 months of System User + Google Suite Plus
Apply for the programme →
for marketplace reviewers

Reviewer hotline

Direct line to the publisher for the OAuth-scope review. We respond within one business day with screen recordings, scope justifications, and reference architecture documentation.

for workspace admins

Security review call

30-minute call to walk through OAuth scopes, data residency, audit-log retrieval, and the revocation path. Tailored to your compliance posture.

for prospect customers

Featured customer pitch

First three MROs onto Google Suite Plus get the co-marketing package: Google customer story, joint webinar, Cloud Next slot, six-month discount.