Automations3 min read / Beginner / Needs code: no
Build a first no-code automation for meeting notes
Set up a first Make scenario that turns a new meeting notes file into short notes and action items, then emails them to you. Here is the order of steps and what Make's help pages say about limits.
What it is
An automation is a workflow that runs by itself when something happens. In Make, an automation is called a scenario. Make's help pages describe a scenario as a series of modules that show how data moves and changes between apps. Here, a new meeting notes file starts it, an AI module writes short notes and action items, and an email module sends them to you.
Who it is for
This is for managers, assistants, project leads and anyone who sits in many meetings and then has to write the follow-up. It also helps if you want your first no-code automation and prefer a small, clear job to start with.
What you need
- A Make account. Make's help pages say it is free to create.
- An account for the app where your notes or transcript files appear. Make's help pages list Google Drive and Google Docs among popular apps.
- An account for an AI app. Make's help pages list Anthropic Claude and OpenAI among popular apps.
- An email account that Make can send from. Gmail and Email are both listed among popular apps.
- Make's help pages do not say which Make plan the AI modules need. Check this in your account before you start.
Set it up
Make's first scenario guide has ten steps. Its own example sends a Slack message when a new row appears in a Google Sheet. The steps below follow the same order, applied to meeting notes. The detail inside each step depends on the apps you choose, so open the matching Make help page as you go.
- Plan your scenario. Write down what starts it (a new notes file), what should happen (short notes and action items) and where the result goes (your inbox).
- Get your apps ready. Make sure you can sign in to your notes app, your AI app and your email.
- Add your first app. In Make, start a new scenario and add the app where your notes files appear.
- Create a connection. Connect that app to your Make account when Make asks.
- Set up the trigger. The trigger is the module that starts the scenario. Choose the event that fits a new notes or transcript file.
- Test the module. Run it once and check that Make finds your file.
- Add another module. Add the AI module first, then the email module.
- Map data. Pass the text of the notes into the AI module. Then pass the AI's answer into the body of the email.
- Test your scenario. Run the whole chain once with a real notes file and read the email you receive.
- Schedule your scenario. Choose when it should run.
A first thing to try
In the AI module, type this as your instruction. Then map your meeting text where Make asks for the input.
Read the meeting notes below. Write a summary in five bullet points or fewer. Then list the action items. For each one, give the owner and the due date if the notes mention them. If something is not in the notes, write "not stated".
Send the first few results to yourself only. Read them against the original notes before you share anything with your team.
Limits and privacy
- Each team can create up to 100 scenarios per day.
- Each scenario has a size limit of 2 MB.
- Make's help menu has a section called Credits & operations. The page for first scenarios does not explain it, so read it before you run the scenario often.
- Make's help menu also has pages called Securing data with Make and AI providers and data zones in Make. Read them before you send private meeting content through an AI module.
- Make's help pages do not say how accurate the AI notes will be. Check them yourself.
Start with one meeting and one notes file, and build from there.
Where these steps come from
Steps from Make's documentation, checked 13 Nov 2026.
This guide was written by AI from the pages above. Menus and plans change, so open them if a step looks different.