Zoom to Google Drive, recordings filed and searchable
Zoom recordings are easy to create and oddly hard to manage. They land in different places, names don’t match topics, and the one call you need always seems to be “somewhere in the cloud.”
This hits marketing leads and ops managers first, because they’re the ones hunting for proof, quotes, and training clips. Agency owners feel it too. A solid Zoom Drive automation turns every finished recording into a clean file in Google Drive plus a searchable Airtable log you can actually report on.
Below, you’ll see how the workflow routes each recording, what it captures, and the real outcomes you should expect once it’s running.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Zoom to Google Drive, recordings filed and searchable
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Create or update a record"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Log Result"]
n2@{ icon: "mdi:cog", form: "rounded", label: "Upload to Google Drive", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Download Recording"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Normalize Recording Data"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Zoom Recording Webhook"]
n1 --> n0
n3 --> n2
n2 --> n1
n5 --> n4
n4 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 database
class n3,n5 api
class n1,n4 code
classDef customIcon fill:none,stroke:none
class n0,n1,n3,n4,n5 customIcon
The Challenge: Zoom recordings that disappear when you need them
After a call ends, the real work starts. Someone has to download the recording, name it in a way that makes sense later, upload it to the right Google Drive folder, then message the team or update a tracker so people can find it. And when it doesn’t happen right away, it usually doesn’t happen at all. A week later you’re searching through Zoom, Drive, Slack, and email threads trying to match “Meeting Recording” to a client name, and you still aren’t sure you found the right version.
It adds up fast. The friction compounds.
- Recordings get stored inconsistently, so “where we keep calls” changes depending on who hosted the meeting.
- Manual downloads and uploads take about 10 minutes per meeting, and that’s before renaming or sharing.
- Meeting metadata lives in people’s heads, which means reporting on calls becomes a guessing game.
- When you finally need an old call (sales proof, compliance, onboarding), you waste time and still worry it’s the wrong file.
The Fix: Automatically file every Zoom recording and log it in Airtable
This workflow listens for Zoom’s recording.completed event, then takes over the boring parts immediately. When a meeting finishes and Zoom publishes the recording, n8n receives the webhook payload with the meeting details (meeting ID, topic, host, file type, file size, timestamps). A short “cleanup” step normalizes that data so it’s consistent every time, even if Zoom’s payload varies slightly between meeting types. Next, n8n downloads the actual recording file via HTTP Request and uploads it straight into the Google Drive folder you choose. Finally, it combines the Drive file link and ID with the meeting metadata and upserts a row in Airtable, so your “Meeting Logs” table stays accurate without duplicates.
The workflow starts when Zoom signals the recording is ready. Then it standardizes the metadata, fetches the recording, and stores it in Drive. Airtable becomes your searchable index, while Drive stays your single archive.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say your team runs 15 Zoom calls a week (sales demos, onboarding, delivery check-ins). Manually saving each recording is usually about 10 minutes per meeting between download, upload, naming, and pasting a link into a spreadsheet, so you lose about 2.5 hours weekly. With this workflow, the “work” is basically zero after setup: Zoom triggers it, the file uploads in the background, and Airtable updates automatically. You still wait for processing, but you’re not doing it.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Zoom to send recording.completed webhooks.
- Google Drive to store recordings in a chosen folder.
- Airtable to keep a searchable “Meeting Logs” table.
Skill level: Intermediate. You’ll paste a webhook URL into Zoom, connect OAuth accounts, and map fields to Airtable columns.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Zoom finishes a recording and pings your webhook. The “Incoming Zoom Webhook” node receives the recording.completed event, which includes the meeting’s metadata and file references.
The meeting data gets cleaned up. A short code step standardizes fields like meeting ID, topic, host, file type, file size, and timestamps so your downstream steps don’t break when a field is missing or formatted differently.
The recording file is downloaded and saved. n8n uses an HTTP Request to fetch the recording binary, then the Google Drive node uploads it into your destination folder (the one you set with your folder ID).
Airtable becomes the index. Another code step assembles the Drive file ID and share link with the original Zoom metadata, and the Airtable node upserts a record into your “Meeting Logs” table.
You can easily modify the Google Drive folder structure and the Airtable fields you capture based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
Set up the incoming Zoom webhook so recordings can be captured as soon as Zoom notifies your workflow.
- Add the Incoming Zoom Webhook node and set HTTP Method to
POST. - Set the Path to
zoom-recording. - Copy the test webhook URL from Incoming Zoom Webhook and register it in your Zoom webhook settings for recording events.
Step 2: Set Up Recording Data Normalization
Normalize the Zoom payload so downstream nodes can use consistent fields.
- Add the Standardize Recording Data node after Incoming Zoom Webhook.
- Paste the provided JavaScript into JavaScript Code (this extracts
meeting_id,topic,host,file_url,file_type,file_size, andtimestamp). - Verify the output includes
file_urlbecause it will be used by Fetch Recording File.
recording_files[0], the code will fail. Ensure the Zoom event is configured to include recording files.Step 3: Download the Recording and Store It in Google Drive
Fetch the recording from Zoom and store it in your Drive for archiving.
- Add Fetch Recording File after Standardize Recording Data and set URL to
={{ $json.file_url }}. - Add Store File in Drive after Fetch Recording File.
- Set Drive to
My Driveand Folder to/ (Root folder)in Store File in Drive.
Step 4: Assemble Metadata and Log to Airtable
Combine the Drive upload details with the normalized Zoom data, then upsert a row in Airtable.
- Add Assemble Drive Metadata after Store File in Drive and keep the provided JavaScript, which merges Drive and Zoom fields.
- Add Upsert Airtable Entry after Assemble Drive Metadata.
- Set Base to
[YOUR_ID]and Table to[YOUR_ID](example:Zoom Meeting Log). - Configure the column mappings in Upsert Airtable Entry:
- Set Host to
={{ $json.host }}, Topic to={{ $json.topic }}, File Size to={{ $json.file_type }}, File Type toOther, and Meeting ID to={{ $json.meeting_id }}. - Credential Required: Connect your airtableTokenApi credentials in Upsert Airtable Entry.
Step 5: Test and Activate Your Workflow
Run a live test to confirm the full flow from Zoom to Drive and Airtable.
- Click Execute Workflow and trigger a Zoom recording event to hit Incoming Zoom Webhook.
- Confirm Store File in Drive creates a file in the selected Google Drive folder.
- Verify Upsert Airtable Entry creates or updates a row with the recording metadata.
- When tests succeed, toggle the workflow to Active for production use.
Watch Out For
- Zoom webhook validation and event permissions can trip you up. If the workflow doesn’t trigger, check your Zoom app’s Event Subscriptions dashboard and confirm recording.completed is enabled.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Drive uploads can “succeed” into the wrong place if the folder ID is incorrect. Confirm the destination folder ID and verify the connected Google account has access before you trust the archive.
Common Questions
Usually about an hour once your Zoom app and Airtable table are ready.
Yes. You won’t write “real code,” but you will connect accounts and paste IDs (like your Google Drive folder ID) into the right spots.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Zoom, Airtable, and Google Drive plan limits (most teams are already covered).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
You can keep the same backbone (webhook → download → Drive → Airtable) and swap the details. Common customizations include changing the destination folder in the “Store File in Drive” node, adding extra fields in “Assemble Drive Metadata” for client name or project code, and adjusting the Airtable upsert logic so it keys off Meeting ID plus recording type.
Most of the time it’s not “Zoom credentials,” it’s the webhook setup. Confirm your Zoom app is publishing the recording.completed event, then check the Event Subscriptions log for delivery errors. If Zoom is sending events but n8n shows nothing, your webhook URL may be blocked by auth, changed, or not reachable from the public internet. And if downloads fail later, the recording file URL may require the right Zoom scopes or a refreshed token.
On self-hosted n8n there’s no execution cap, so capacity mostly depends on your server and how large your recordings are.
Often, yes, because this flow is file-heavy and metadata-heavy, and you may want tighter control over naming, folder routing, and upsert logic. n8n handles branching and data shaping without making every extra step feel like a tax, which is honestly where a lot of teams get frustrated with simpler “two-step” tools. Also, self-hosting means you can run as many executions as your server can handle, which is useful if you have lots of calls. Zapier or Make can still be a fine choice for lightweight logging, especially if you’re allergic to any setup beyond clicking buttons. Talk to an automation expert if you want a quick recommendation for your exact stack.
Once this is running, your recordings stop being a scavenger hunt and start being an asset. The workflow handles the repetitive filing and logging so you can get back to work that actually moves things forward.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
