# I built an AI-assisted meeting follow-through system using Make, OpenAI and Google Workspace **URL:** \ **Category:** Knowledge Hub\ **Tags:** gmail, make-automation, open-ai, google-sheets, ai\ **Created:** [November 2, 2026, 11:55am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049 "2026-11-02T11:55:58Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Kanika](https://avatars.discourse-cdn.com/v4/letter/k/4bbf92/32.png) [@Kanika](https://community.make.com/u/Kanika)\ **Post date:** [November 2, 2026, 11:55am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049/1 "2026-11-02T11:55:58Z")
I would like to look at something that is frequently ignored in the automation of meetings. It is useful to record what has been discussed, but how can we ensure that the decisions actually result in action? I created a workflow that uses AI to link together the notes from meetings with action tracking, deadline monitoring, and change management. **How it works** 1. **Meeting Notes Intake:** Meeting notes are entered via a Google Form. 2. **AI-assisted extraction:** OpenAI looks over the notes to detect the action items that have been suggested and arranges them in a uniform format. 3. **Human review:** The proposed actions are placed in a Review Queue so that a person can check and approve them before they are included in the Action Register. 4. **Deadline monitoring:** Keep an eye on the deadlines that are coming up and prepare draft emails to be sent via Gmail for review. 5. **Change Log:** The updates relating to the tracked actions are kept so that any changes made to the original plan can be seen. 6. **Follow-up dashboard:** This provides a central overview so that you can keep track of the actions still needed, the deadlines, and the progress. One aspect that I especially wanted to look at was the Change Log. ![Action updates fed into form routed to relvant field in Change Log](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/8/9/89051266e26f6b25160d404dcb442f8aee1bd91d.png) ![Change Log Tracker Updates](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/a/7/a7c1394d50939bb26986ed3945dc5d11c4a33b2b.png) The plans for a project rarely remain precisely the same as those agreed upon in the initial meeting, for priorities may change, deadlines may be altered, and the actions may be modified. It is more difficult to tell whether the present action plan still agrees with the original decisions if there is no record of the changes. The Change Log offers insight into the way the plan develops. It enables people to see what changes have been made and to decide whether the current commitments are still in line with the agreed direction. It does not automatically make that decision. The aim is to provide people with a clearer record based on which they can work. **A few design decisions behind the workflow:** The AI suggests courses of action, but a person has to approve them. - Emails sent as follow-ups are prepared in draft form and are not automatically sent. - Changes are kept on record rather than simply overwriting the original plan. The dashboard shows progress on various actions in one place. I used Make, OpenAI, and Google Workspace, focusing on practical automation and human supervision rather than building another meeting summariser. I’m attaching a brief walkthrough which shows how the workflow fits together. **I’d be interested to hear from other Makers:** What is your approach when it comes to altering action items or deadlines after a meeting? Do you keep a separate change history, or do you make the changes directly in the action tracker? ---
**Author:** ![Mahdi\_Eqbal](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mahdi_eqbal/32/93743_2.png) [@Mahdi\_Eqbal](https://community.make.com/u/Mahdi_Eqbal)\ **Post date:** [November 3, 2026, 6:17am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049/3 "2026-11-03T06:17:00Z")
I’d keep the approved action as a separate record from the AI’s original suggestion, then treat later changes as revisions rather than overwriting it. For each change, I’d capture the previous value, the new value, who approved it, when it took effect, and why it changed. That makes it much easier to distinguish a legitimate deadline extension from an overdue action that was quietly rescheduled. One edge case worth handling is when meeting notes mention an action that’s already open. Matching it to the existing action before creating a new one could prevent duplicate commitments across recurring meetings. ---
**Author:** ![Stoyan\_Vatov](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@Stoyan\_Vatov](https://community.make.com/u/Stoyan_Vatov)\ **Post date:** [November 3, 2026, 8:42am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049/4 "2026-11-03T08:42:05Z")
Why are you using polling triggers instead of instant ones? And why are you parsing the output of the OpenAI module separately? Its a built in function. Both of these are wasting operations. ---
**Author:** ![Kanika](https://avatars.discourse-cdn.com/v4/letter/k/4bbf92/32.png) [@Kanika](https://community.make.com/u/Kanika)\ **Post date:** [November 3, 2026, 9:59am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049/5 "2026-11-03T09:59:07Z")
Thanks for sharing this! I reviewed your suggestions against the workflow design, and quite a few of these controls are already part of it. The Change Log is designed to capture the Action ID, change date, field being modified, previous value, new value, reason for the change, and the person making the update. The Action Update Form collects these details before Make updates the Action Register and creates a separate Change Log entry. The intention is exactly what you described: retain a traceable history of changes rather than silently overwriting the original information. This makes it possible to understand how an action or deadline has evolved. Your suggestions about explicitly capturing the approver and effective date are useful additions to consider. I also account for possible duplicate actions through AI-generated duplicate flags and human review, although automated matching against existing open actions is something that could be developed further. Appreciate the thoughtful feedback! ---
**Author:** ![Kanika](https://avatars.discourse-cdn.com/v4/letter/k/4bbf92/32.png) [@Kanika](https://community.make.com/u/Kanika)\ **Post date:** [November 3, 2026, 10:11am UTC](https://community.make.com/t/i-built-an-ai-assisted-meeting-follow-through-system-using-make-openai-and-google-workspace/119049/6 "2026-11-03T10:11:36Z")
Thanks for pointing these out! I agree on the trigger. An instant trigger would be more efficient here, as it can initiate the workflow as soon as a new submission arrives, avoiding repeated polling checks. That’s definitely something worth optimising. Regarding JSON parsing, I used the OpenAI Simple Text Prompt module, which returned the generated output as text. I added the Parse JSON module to convert it into structured data so the Iterator could process each proposed action individually. I understand that native structured output can potentially eliminate this extra step, but I used explicit parsing to make the output available for the next stages of the workflow. I am new to this and still learning. Your feedbacks would be very helpful for me. Thanks for highlighting these. I’ll keep them in mind when optimising the workflow further!