Building an automated meeting minutes pipeline in Make.com using Clova Note → Google Drive → Claude AI → Google Docs, but hitting a wall with personal Google account connectivity

Questions
, ,
1

:bullseye: What is your goal?

I want to automate the entire meeting minutes workflow using Make.com:
Step 1 – Audio to Text: Record meetings using NAVER Clova Note, which auto-transcribes speech to text. After the meeting, I export it as a Google Docs file.
Step 2 – Trigger: The exported Docs file lands in a pre-designated Google Drive folder. Make.com watches this folder and triggers the scenario when a new file is detected.
Step 3 – Content Generation: Claude reads the raw transcription file and generates a structured, formatted meeting minutes document based on a custom user prompt (agenda summary, decisions made, action items, etc.).
Step 4 – Save Output: The generated meeting minutes are saved as a new Google Docs file into a separate subfolder within the same Drive directory.
Step 5 – Notification: A completion email is sent to notify that the meeting minutes are ready.

:thinking: What is the problem & what have you tried?

The blocker is at Step 2 — connecting Google Drive in Make.com using a personal Google account.

My company does not use Gmail/Google Workspace, so I only have access to a personal Google account.
When I try to connect Google Drive in Make.com with my personal account, the connection either fails or doesn’t behave as expected.
I asked Gemini and it suggested some workarounds, but when I actually tried to implement them, the connection still didn’t work properly.

What I need to know:

Is it possible to connect a personal Google account to Make.com’s Google Drive module reliably?
If yes, what is the correct OAuth setup or permission configuration to make it work?
Are there any known limitations or alternative approaches (e.g., using Google Drive API directly, using a different trigger module) that would bypass this issue?

:clipboard: Error messages or input/output bundles

No specific error message captured yet — the issue occurs during the OAuth connection setup phase between Make.com and my personal Google Drive account. The connection appears to go through initially but either fails to detect new files in the watched folder, or the module doesn’t authenticate correctly. Will attach screenshots of the module configuration and error state if needed.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

Meeting Summary scenario.png
Meeting Summary scenario.png1225×362 43.4 KB

4

Hey @i_isjung !

A personal Google account can be connected to the Google Drive modules in Make. You do not need a Google Workspace account for this. Normally you can just create the connection through the module and approve access during the Google login step.

One thing that often causes confusion is the trigger you’re using. “Watch Files in a Folder” does not trigger instantly. It checks the folder on a schedule. Because of that, it may look like the connection isn’t working when the scenario simply hasn’t checked the folder yet.

A couple of things worth checking:

Reconnect the Google Drive connection from scratch and select your personal account again.

Make sure the scenario is turned on and scheduled to run.

After turning the scenario on, upload a completely new file to the watched folder. The module usually only detects files added after the scenario is active.

Also confirm the folder you selected is inside “My Drive” and not a shared or special folder.

If the connection itself is failing during login, it usually helps to remove the existing connection in Make and create a new one.

Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard

1 Like
5

Hi, @Tuesday_Wizard

Thank you so much for your help, including my previous question. I’ll take your feedback into consideration and revise the scenario accordingly.

6

Yes, a personal Google account can work with Make’s Google Drive modules.

If the connection signs in but the folder watch is unreliable, I’d first try re-creating the Google Drive connection from scratch and reselecting the folder. If that still acts up, Make’s own docs suggest using a custom Google OAuth client for Google Drive/Sheets when the standard connection is problematic.

So in practice:

  • personal Google account = supported

  • if the built-in connection is flaky, use a custom OAuth client

  • if “Watch files in a folder” connects but finds nothing, also double-check the watched folder itself and test with a newly added file after the scenario is turned on

That’s probably the cleanest path here.