Real use case

Meeting notes turned into tracked actions in Make

A Make Community member built a workflow that turns meeting notes into actions people actually follow up on. Notes go in through a Google Form. OpenAI picks out the suggested action items and puts them in a standard format, but they land in a review queue, and a person approves them before they reach the action register. The workflow watches deadlines and prepares Gmail follow-up drafts for review instead of sending them. A change log keeps every update, so you can see how the plan drifted from what the meeting agreed, and a dashboard shows open actions and deadlines in one place. Her design choices are worth copying: the AI suggests, a person approves, and nothing is sent automatically.

AgentMake

Copy this prompt

Help me plan a Make scenario: when a Google Form with meeting notes is submitted, send the notes to an AI module that lists action items as owner, task and due date. Put each item in a Google Sheet tab called Review. When I mark a row Approved, copy it to an Actions tab. Every morning, find actions due in [DAYS] days and create a Gmail draft (not a send) to the owner. Log every change in a Change Log tab. List each module and what to test.

Our own prompt, written from what the source describes. We haven't run it ourselves. Text in [BRACKETS] is what you replace.

Watch out for

  • Keep the human review step. AI can invent an owner or a due date that nobody agreed to.
  • Leave follow-ups as drafts, as she did, until you trust the output.
  • Each AI step uses Make credits. Check how many a test run uses before you turn it on for every meeting.

Where this comes from

Original post by Kanika on Make Community, Nov 2, 2026. We rewrote it in our own words. The result is what the poster reports.

Read the original

Guides for this job

Email & workPrompt run 2026-10-19

Turn a messy inbox into a 5-minute daily summary

Paste in today's emails and get back what needs a reply today, what can wait, what to ignore, and a one-line reply for each. It also flags emails that look like scams.

ChatGPTClaudeGeminiGrok
Prompt guide
Keep going

More like this

Real use caseEmail & work

An OpenClaw assistant with a Telegram topic for each job

He runs a personal assistant on OpenClaw that lives in one private Telegram group, with a separate topic for each kind of work. New emails land in a Gmail topic within a minute, and he can ask it to write and send an email, but nothing goes out until he approves it. There's a topic for business ideas and plans, a news digest that arrives every night, reminders on request, quick summaries of PDFs he drops in, the main points of links he shares, and descriptions of screenshots. Only his account can use it, shell commands are locked down, and his keys stay on his own server. He also offers to set this up for others for a fee, so treat the post partly as an ad; the setup itself is a sensible pattern.

PromptHelp me set up my OpenClaw assistant in one private Telegram group with these topics: Email (post a one-line...

OpenClaw
Copy prompt
@anikanik4455 on X · Nov 1, 2026
LessonEmail & work

Audit your agent's routines before they eat your usage

He asked Grok Bot for a read-only check of all his routines: find duplicates, and routines that run more often than they need to, then recommend keep, merge or cut for each one, without changing anything until he approves. It's a good habit with any agent that runs scheduled jobs. A routine that runs every hour when once a day would do uses up your weekly allowance, and two routines doing the same check do it twice.

PromptList every scheduled routine you run for me, with how often it runs and what it does. Point out any that...

Grok Bot
Copy prompt
@Michael_Fenech_ on X · Nov 1, 2026
LessonEmail & work

Make: why a Todoist webhook ignored finished tasks

On the Make Community forum, someone wanted a scenario to run whenever they checked off a task in Todoist. Their webhook fired when a task moved between sections, but nothing happened when a task was marked complete. A forum helper explained why: in Todoist, finishing a task is its own event, called item:completed, separate from item:updated. So you add that event to the webhook and give it its own route with a filter in the scenario. Recurring tasks are the trap. Checking one off just moves it to the next date, so Todoist sends an update event instead, marked with a completed intent. The original poster hadn't confirmed the fix yet, but Todoist's own documentation describes the events the same way. The general lesson for Make: when a trigger doesn't fire, check which exact events the app sends, because "changed" and "finished" are often separate.

PromptHelp me set up a Make scenario that runs when I check off a task in Todoist. Tell me which Todoist webhook...

Make
Copy prompt
Amayensis on Make Community · Oct 31, 2026