Import meetings automatically
Connect Google Meet once, and every call that Google transcribes or takes notes for becomes a page in your workspace's Meetings folder by itself, within about 5 to 10 minutes of Google finishing the transcript or the notes. In a hurry? Check for new meetings runs the script right away.
It works with a small Google Apps Script that runs in your own Google account. Markdrop writes the script for you; you paste it into Google once. You can still import meetings manually at the same time.
Before you start
#- You're a member of the workspace (not a viewer).
- Google Meet saves a transcript (Transcripts on in the call) or Gemini's notes (Take notes for me). They're saved to the Drive of the person who turned them on, usually the organizer, and shared with the people invited.
- You're signed in to Google with the account you join your calls with. You don't need to be the organizer: the script also finds the meetings shared with you.
Connect Google Meet
#-
In the workspace's Meetings folder, select Connect Google Meet in the bar at the top. It opens the Meetings page with the dialog. On the Meetings page itself, Connect Google Meet sits next to Import meeting (and in the ⋯ menu).
-
Under Also import past meetings from your Drive, choose how far back to go: No, only new meetings, or the Last 7, 30 (the default) or 90 days. See Past meetings.
-
Leave Include meetings shared with me on to import every meeting you attended, including the ones someone else organized. Switch it off to import only the Docs in your own Drive.
-
Optionally switch on Only the people in each meeting can open its page. See Restricted meetings.
-
Select Make my script. Markdrop shows a manifest and a script, each with a Copy button, and the four steps below. The script holds a token that only works for importing meetings into this workspace. It's shown this once.
Then, in Google:
- Open Apps Script. Go to script.google.com and create a New project.
- Paste the manifest. In Project Settings (the gear), tick Show "appsscript.json" manifest file in editor. Back in the Editor, open
appsscript.jsonand replace everything in it with the manifest you copied. - Paste the script. Open
Code.gs, replace everything in it with the script you copied, and press Save. - Run setup once and allow. Pick
setupnext to Run and press Run. Google asks you to allow the script. Because it's your own script, Google shows Google hasn't verified this app: select Advanced, then Go to … (unsafe), then Allow.
setup imports the meetings of the last 48 hours straight away, starts on the past meetings you chose, and schedules itself every 5 minutes. Back in Markdrop, the Meetings page shows Google Meet connected, when it last imported and how many meetings it brought in (or waiting for the script's first run until setup has run), and how the script's last run went (see See what the script found). The Meetings folder shows the same line in its bar.
When other members connected their own scripts to this workspace, the line says so: Also importing here: and their names.
What the script can see and do
#- It reads only meeting Docs. It looks at Google Docs whose title looks like a Meet transcript ("Meeting name (date) - Transcript") or Gemini's notes ("Meeting name - date - Notes by Gemini"), created in the last 48 hours. Google's titles in other languages count too ("Transcripción", "Notizen von Gemini" and so on), and so does any Doc in a Meet Recordings folder. Other files are never opened.
- Yours and the ones shared with you. A meeting someone else organized lives in their Drive and is shared with the attendees: the script finds those too, and Docs in shared drives (that part is optional: see Shared-drive search is off). Someone else's Doc must look like Meet's own (Gemini's notes, or the call's date and time in the title), so a teammate's "Plan - Notes" isn't sent. With Include meetings shared with me off (
INCLUDE_SHARED = falseat the top of the script), only Docs you own are sent. - Once per call. When several attendees connect, a call's Doc is imported once: the second script's copy is recognized as the same Drive file (or the same call) and skipped.
- Read-only. Google grants it read-only Drive access (
drive.readonly), permission to call Markdrop (script.external_request) and to schedule itself (script.scriptapp). It never edits, moves or deletes anything in your Drive. - Its own token. The token in the script can only send meetings to this workspace's inbox. It can't read your documents, act as you anywhere else, or be used with the API or MCP. It isn't listed with your API tokens, and the meetings it imports are yours, as if you had imported them.
- It waits for Google to finish. A Doc that changed in the last 5 minutes is sent on the next run, so a Doc Google is still writing isn't imported half done.
- Gemini's notes arrive when Google fills them in. Gemini makes its notes Doc when note-taking starts and writes the notes when the call ends. While the Doc is still empty, Markdrop answers not ready and the script sends it again as soon as Google changes it. A Doc with nothing in it 12 hours after Google made it is left alone.
- Changes come through. When Google (or someone) changes a Doc after it was imported, the script sends it again and the meeting takes the new notes or the longer transcript: the page is written again when nobody edited it, otherwise the new notes are added at the end, and the summary is written again. A Doc is sent again at most 5 times. A meeting you deleted isn't made again.
See what the script found
#Each run tells Markdrop how it went, and the Meetings page shows it under Google Meet connected:
Script ran 5 min ago · found 2 meeting Docs · sent 2 · 14 skipped: 12 not titled like Meet, 2 still being written
- Found is the meeting Docs the run could send; sent is how many it sent (Docs it sent before aren't counted again).
- Skipped says why the other Docs it looked at were left out: not titled like Meet, shared with you (not included), older than it looks back, still being written (sent next run). Markdrop only gets these counts, never the skipped Docs or their names.
- Waiting for Gemini's notes: "1 meeting waiting for Gemini's notes or the transcript — sent as soon as Google fills it in" is a call whose Doc Google hasn't written yet (the call may still be on). Nothing to do: it arrives on the run after Google writes it.
- Updated: meetings that took newer content from a Doc Google changed.
- More in the next run: a run sends for about 4½ minutes (Google stops a script at 6), so a big pile of Docs takes a run or two. The line then says how many wait: "sent 60 of 79 · 19 more in the next run (every 5 min) — or run syncMeetings now".
- A Doc the script couldn't read, or Markdrop turned away, shows as an error with its title.
- Shared drives aren't searched is a hint, not an error: see Shared-drive search is off.
To see the list itself, open the project in Apps Script, pick check next to Run and press Run. It lists every Doc it would send (WOULD SEND) and why it skips the others, in the Execution log, and sends nothing. The Meetings page then shows the counts as Checked 5 min ago instead of Script ran.
When the last run found nothing, the page says what to look at: meetings left out because they're shared with you (make a new script with Include meetings shared with me on), or, with nothing at all, whether transcription or Take notes with Gemini is on in your calls.
Check for new meetings
#The script checks every 5 minutes by itself. Right after a call, you don't have to wait: on the Meetings page, select Check for new meetings (on phones it's in the ⋯ menu; on Home, under Meetings). The connected scripts run at once, and Markdrop says what arrived: "Found 1 new meeting.", "No new meetings.", or that Google hasn't filled in the notes yet. Any member can press it, once a minute per workspace. The line under Google Meet connected shows when it last checked.
Markdrop can't look in your Drive itself, so it asks your script to run. Turn this on once, as the person who connected Google Meet (the button says Turn on Check now until you do):
- Open your project at script.google.com. It needs script version 4 or later: update it first if the Meetings page says New script.
- Select Deploy, then New deployment. Next to Select type, select the gear, then Web app.
- Set Execute as to Me and Who has access to Anyone, and select Deploy. Allow it if Google asks.
- Copy the Web app URL (it ends in
/exec), go back to Markdrop, paste it under Turn on Check now and select Turn on Check now.
Anyone only means Google doesn't ask for a sign-in: the web app does nothing unless the caller sends a key that only Markdrop and your script have, it runs at most once a minute, and it can only send your meeting Docs to your workspace, like the schedule does. The address is never shown to anyone else in Markdrop. To turn it off, delete the deployment (Deploy › Manage deployments › Archive).
When you paste a newer script later, update the deployment too: Deploy › Manage deployments › edit (pencil) › Version: New version › Deploy. The URL stays the same.
If a check fails, Markdrop says why: Google asks for a sign-in (set Who has access to Anyone), the deployment runs an older script (deploy a New version), or the script was busy with its scheduled run (its meetings arrive in a minute or two).
Update the script
#The current script is version 4: the top of Code.gs says script version 4. When yours is older, the Meetings page shows New script with Get the new script. Update it:
- Version 1 (before November 5, 2026) doesn't import meetings shared with you and doesn't report its runs, so the line under Google Meet connected stays empty.
- Version 2 sends at most 20 Docs a run and warns when the Drive API is off. Version 3 sends as many as a run has time for and says it once a day, as a hint.
- Version 3 runs every 15 minutes and sends a Doc only once, so Gemini's notes sent while the call was still on (an empty Doc) never arrived. Version 4 runs every 5 minutes, sends a Doc again when Google fills it in or changes it, and adds Check for new meetings. On its first run it sends once more the Docs version 3 sent in the last 48 hours, so a meeting that was missed then arrives now (the ones already imported are recognized and left as they are).
To update:
- Select Get the new script (or New script), choose your options and select Make a new script. The old script's token stops working.
- Open your existing project at script.google.com, replace everything in
Code.gswith the new script and press Save. The manifest hasn't changed. - Pick
setupnext to Run and press Run. That also moves the schedule to every 5 minutes. - If you turned on Check now, update its deployment: Deploy › Manage deployments › edit (pencil) › Version: New version › Deploy.
Past meetings
#When you connect, the script can also bring in the meetings already in your Drive: the last 7, 30 or 90 days.
- Oldest first, as many as a run has time for (about 4½ minutes, at most 200 Docs), so a long history takes a run or two, 5 minutes apart. To send the next batch right away, pick
syncMeetingsnext to Run and press Run. The script's log in Apps Script says Backfill finished when it's done. - Nobody is notified. A past meeting's action items still name their owners, and the @mentions are links, but no one gets a notification or an email about them (that's true of every meeting), and a call that's long over isn't posted to your Slack meetings channel. Meetings from the last 48 hours are posted as usual.
- Dated by the call, not by the import: the date in Google's title, or when Google made the Doc. The Meetings page lists them by date, and each goes into its series' folder. See How meetings are organised.
- No duplicates. Meetings already in the workspace, imported by hand or by an earlier run, are skipped.
To go further back later, open the script, pick backfill next to Run and press Run. It goes back BACKFILL_DAYS days (set at the top of the script; 30 when it's 0). To choose another number, change BACKFILL_DAYS first.
Notes and transcript become one meeting
#Google often saves the notes and the transcript of a call as two Docs, a few minutes apart. Whichever arrives first makes the meeting; the other is added to it when it arrives, by the meeting's name, date and start time. The page and its summary are updated with it.
There are no duplicates with manual import either: a Doc you already imported by hand, or a call that's already in the workspace, isn't imported again. See No duplicates.
Disconnect
#On the Meetings page, select Disconnect next to Google Meet connected. The script's token stops working at once; on its next run the script sees that and removes its own schedule. Meetings it already imported stay. You can also delete the project at script.google.com.
Each person has one connection. New script (or connecting in another workspace) replaces it, and the old script stops working.
If you leave the workspace, or become a viewer in it, the script stops importing: Markdrop turns its Docs away until you connect again.
Troubleshooting
#Google says "Google hasn't verified this app"
That's expected for a script you wrote yourself: only apps published to other people are verified. Select Advanced, then Go to … (unsafe). The permissions it asks for are the three listed above.
Nothing shows up
- Look at the line under Google Meet connected: it says what the last run found and why it skipped Docs. No line at all means the script hasn't run yet, or it's an older script: update it.
- shared with you (not included): the meetings were organized by someone else. Make a new script with Include meetings shared with me on.
- not titled like Meet: Google's own names ("… - Transcript", "Notes by Gemini") are what the script looks for. A renamed Doc is skipped; import it manually or paste its link instead.
- Found 0 and nothing skipped: no Meet Docs reached your Drive in that time. Check that transcripts or Take notes for me are on in your calls, and that the organizer shares the notes with attendees (Google's default for people in the same organization).
- In Apps Script, run
checkto see the list, or open Executions to see each run's log: what it sent and what Markdrop answered. - A meeting from a few minutes ago: Gemini writes its notes when the call ends, and the script sends the Doc on the next run after that (every 5 minutes). The line says waiting for Gemini's notes meanwhile. Select Check for new meetings to send it right away.
- Still on script version 3? It could miss Gemini's notes for good (it sent the Doc while it was empty). Update the script: version 4's first run sends those Docs again.
- A Doc without a transcript or notes in it (an empty one, or a shopping list called "… - Notes") is retried while Google may still write it (12 hours), then counted as ignored.
Shared-drive search is off (the Drive API message)
The script's log may start with: Shared-drive search is off (optional: enable the Drive API for this script's project: …). Using your Drive and files shared with you — meetings shared with you are still imported. The Meetings page shows the same as a small hint: Shared drives aren't searched.
Nothing is wrong. Google leaves the Drive API off in a new script's own project, and the script only needs it to look in shared drives (and in Meet Recordings folders there). Without it, the script searches your Drive and the files shared with you, so your meetings and the ones someone else organized are still imported. The script says it once a day, not every run.
If your team keeps meeting notes in a shared drive, turn it on: open the link in the log (or enable the Drive API on the Meetings page), check that the project number matches the one in the log, and select Enable. The next run searches shared drives too, and the hint goes away.
It found more than it sent
"Sent 60 of 79 · 19 more in the next run" means the run used its time: a run sends for about 4½ minutes (at most 200 Docs; Google stops a script at 6), and the rest wait for the next run, 5 minutes later. Nothing is lost or sent twice. To send the next batch now, open the project in Apps Script, pick syncMeetings next to Run and press Run.
To send fewer per run, set var MAX_PER_RUN at the top of the script (0, the default, lets the time decide).
Import older meetings
Set var BACKFILL_DAYS at the top of the script to how many days to go back, for example 180 (up to 366), pick backfill and press Run. It continues on its own, a run's worth every 5 minutes, until Backfill finished shows in the log. Meetings already in the workspace aren't imported twice, and nobody is notified about past ones. See Past meetings.
Google's quotas
Google limits how long scripts run each day (about 90 minutes for a personal account, 6 hours for Google Workspace) and how many calls they make. A run that finds nothing new takes a couple of seconds, so 288 runs a day (every 5 minutes) use about 10 to 15 minutes; a run that sends takes longer (up to about 4½ minutes while it catches up on a backlog). A busy calendar stays below them. Markdrop takes up to 30 Docs a minute and 600 a day from one script; more wait for the next run.
My teammate and I both connected
That's fine: each call is imported once. The first script to send it creates the meeting; the other script's copy is recognized (the same Drive file, or the same call by name, date and start time) and skipped, or fills in the half that was missing (Google's notes after the transcript).
It stopped after I disconnected or connected again
Each script works until its token is replaced or revoked. Make a new script with Connect Google Meet, paste it over the old Code.gs, and run setup again.
Related
#- Meetings and Team: how it fits together
- Meetings
- Import a meeting manually
- Privacy and AI
- MCP tools:
meetings_connectiontells an AI app whether automatic import is on, how the script's last run went and how many meetings wait for Gemini's notes, andcheck_meetings_nowchecks for new meetings now.