Integration · Automate and collaborate
Google Workspace and Meteor AI agents
Connect Google Workspace to Meteor: Gmail, Calendar, Drive, Sheets, Docs, Classroom and Search Console in a single tool catalog for your Met.
How does Google Workspace connect to Meteor?
Meteor connects to your Google account through OAuth and gives your Met 32 tools in one catalog: search and send email in Gmail, read the calendar with its attendees and its video link, pull the transcript of a Meet call, search Drive, read and write Sheets, export and read Docs, query Search Console, PageSpeed and the real user experience data for your site, and read Google Classroom: courses, rosters, assignments, submissions and announcements, including who has not turned work in. The eight Classroom tools are read only.
What it automates
What a Meteor Met does with Google Workspace
Make the meeting leave something in writing
Your Met reads the calendar, pulls the transcript of the call that just ended and leaves the summary and the commitments where the team will actually see them.
A report that updates itself
Operating data is appended to a spreadsheet, one row per event, and tabs get created on their own when a new record type shows up.
Decide what to write with data instead of instinct
Your Met crosses the queries already bringing traffic with the pages receiving them, and decides whether to write a new article or update the one that exists.
Confirm Google saw what you published
After publishing, your Met inspects the URL, confirms whether it got indexed and which canonical Google chose, and resubmits the sitemap when that is needed.
Answer "who is missing?" without crossing two lists by hand
A teacher asks about one assignment and your Met crosses the course roster with the submissions: how many turned it in, how many were late, how many are already graded and who has not turned it in, by name. Doing that by hand means two screens and counting.
32 tools
Everything your Met can ask Google Workspace for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
gmail_search | Searches email using the same Gmail syntax you already use. |
gmail_send | Sends an email from the authenticated account. |
calendar_list_events | Lists events between two dates with attendees, organizer and video link. |
meet_transcripts | Returns the transcript of a finished Meet call, when it was recorded with transcription on. |
drive_search | Searches files in Drive by name or, when you ask for it, by content. |
contacts_list | Lists the contacts of the authenticated account. |
sheets_get | Reads visible or unformatted numeric values; calculation ranges are capped at 5,000 rows, 100 columns and 50,000 cells. |
sheets_update | Overwrites cells in a specific range, evaluating formulas. |
sheets_append | Adds rows at the end of a range without overwriting what was already there. |
sheets_write_weekly_report | Writes one approved Mercado Libre weekly row after checking the 13 exact headers and empty dedicated range, with an opaque key, hash, one RAW update using retry:false and a read-back; it never retries blindly. |
sheets_clear | Clears the contents of a range without removing its formatting. |
sheets_metadata | Returns the tabs, the named ranges and the document properties. |
sheets_add_tab | Creates a new tab. If one with that title exists, it neither fails nor duplicates it. |
docs_export | Exports a document to text, PDF, Word, HTML or Markdown. |
docs_cat | Returns the text of a document and says so when it truncates for length. |
gsc_list_sites | Lists the sites verified in Search Console with your permission level. |
gsc_top_queries | Returns the queries with the most clicks, impressions or the best position in a period. |
gsc_pages_with_queries | Returns the top pages together with the queries that bring them traffic. |
gsc_inspect_url | Diagnoses a specific URL and reports whether it is indexed and which canonical Google chose. |
gsc_list_sitemaps | Lists the sitemaps registered, with their errors and warnings. |
gsc_submit_sitemap | Submits or resubmits a sitemap to Search Console. |
gsc_indexing_api_submit | Tells Google a URL was created, updated or removed, to speed up crawling. |
psi_audit | Audits performance and core web vitals for a URL, on mobile and desktop. |
crux_history | Historical series of the real user metrics for a URL or a whole domain. |
classroom_listar_cursos | Lists the Classroom courses the connected account can see, active ones by default, with the id the other tools need. |
classroom_obtener_curso | Detail of one course: name, section, subject, room, state, enrolment code and its link in Classroom. |
classroom_listar_estudiantes | Lists the students enrolled in a course, with their name and internal id. The email comes back empty on purpose. |
classroom_listar_docentes | Lists the teachers of a course, with their name and internal id. |
classroom_listar_tareas | Lists the coursework of a course with its due date, its maximum points and its link. |
classroom_listar_entregas | Lists the submissions of one assignment with their state, whether they were late and what grade they carry, both assigned and draft. |
classroom_resumen_entregas | For one assignment, it crosses the course roster with the submissions and answers in one go how many turned it in, how many were late, how many are graded and who has not turned it in. |
classroom_listar_anuncios | Lists the announcements on a course stream, newest first, with their text, their author and their link. |
The limits
What the Google Workspace integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not reach into other people's accounts in your organization. It runs as the account that authorized it, and only with the permissions granted.
-
It does not return the transcript of a meeting that was not recorded with transcription on. That part depends on how the meeting was set up, not on the integration.
-
It does not administer Google Workspace users, licenses or policies.
-
It does not delete email or files. It searches, reads, sends and writes to sheets and tabs, but it removes nothing.
-
Reading a row and writing it are separate calls, not an atomic operation. The weekly tool rejects an occupied row and reconciles the response, but another concurrent writer could still overwrite it.
-
It does not write to Classroom. The eight classroom tools are read only: no grading, no enrolling, no posting announcements and no creating assignments. Grading would mean asking every account that connects Google for write access to grades, including the ones with no Classroom at all.
-
It does not return a student email address. Meteor never asks for that permission, so a course roster arrives with a name and an id and an empty email field. That is enough to know who has not turned work in and not enough to build a contact list of minors, which is exactly what should not fall out of this by default. A roster in primary or secondary school is children's data: publishing it to a channel is a decision the person publishing it makes.
Before you start
What you need to connect Google Workspace
- 1
Authorization from your Google account
Done once from the Meteor panel through Google sign in. Your password is never requested and never stored.
- 2
Permissions for what you plan to use
Authorizing grants access to Gmail, Calendar, Drive, Sheets and Docs. Search Console and the site metrics also require the site to be verified in your account.
- 3
Reconnecting the account, if you already had Google in Meteor
The five Classroom permissions are new, and a new permission is never granted by itself. Anyone who connected Google earlier keeps working with what they authorized, but the classroom tools will answer with a permissions error until they reconnect the account from Integrations. The account also has to belong to an education domain with Classroom on.
Frequently asked questions
Questions about Google Workspace and Meteor
No. The connection runs through OAuth. You authorize from Google and Meteor receives a revocable grant, never the password.
Only meetings that were recorded with transcription turned on. Your Met takes the meeting identifier from the calendar and pulls the transcript when one exists.
Yes, and it is one of the reasons to connect it. Search Console, per URL index diagnosis, sitemap submission and real user metrics all sit in the same catalog.
Yes: it can overwrite, append, clear content, and use a dedicated weekly write that requires approval and a read-back. Google Sheets does not provide atomic uniqueness between that pre-read and the write.
No. The eight classroom tools are read only: they read courses, rosters, coursework, submissions and announcements, and they never grade, enrol or post anything. That is a decision and not a pending step: asking for write access to grades would force every account connecting Google in Meteor to authorize it, including all the ones with no Classroom.
That is expected, and reconnecting fixes it. The five Classroom permissions are new, so an account connected earlier keeps working with what it authorized back then while the classroom tools report the missing permission. Reconnect the account from Integrations and they light up. The account has to belong to a domain with Classroom enabled.
Step by step
Automations that use Google Workspace
Complete tasks, with the steps and the tools that run at each one.
- Create a weekly Google Ads report in Google Sheets
- Save the weekly Mercado Libre order report to Google Sheets
- Record WhatsApp leads in Google Sheets and leave a traceable follow-up
- A weekly Search Console report, with the history kept
- Answer who did not turn in an assignment, without opening Google Classroom
Documented operations
Customer cases using Google Workspace
Each case states what was manual, what the agent does now, which connectors support it and where the limits are.
Marketing and design agencies · Colombia
The brief stopped living in one person’s head
A digital agency with several years behind it has mature processes and a concentration problem: the person who runs production is the only node connecting the brief, the plan and the delivery. Everything goes through them.
Read the documented caseAgrifood commerce · Colombia
Producing the content stopped being the launch bottleneck
A platform connecting food markets and wholesalers to end consumers reached launch with a finished product and no traction. The problem was not the technology: it was making noise with a small team and a commercial window that does not come back around until next year.
Read the documented case
Want to see a Met running Google Workspace?
We will show you with your own account connected, not with a canned demo.