Make.com Tutorial for Beginners 2026 (Full Guide)

Hey, I'm Matt and in this video I'm going to teach you step by step how to use make.com, a powerful tool that you can use to automate your work, connect your favorite apps, and save hours every week. We're going to set up a simple automation together, and you'll learn everything you need so that by the end of this tutorial, you'll be ready to automate your own tasks using Make. Let me walk you through the exact workflow we'll be building together. We're going to address a common problem that almost every business and freelancer faces using Joe's web design as an example. You see, whenever someone reaches out to Joe through his contact form, he ends up doing the same routine. Copying their info into a spreadsheet, searching for details about their business or website, writing a personalized reply, adding a meeting to his calendar, and then prepping for the conversation. It's a lot of little steps that add up fast. But what if all that could happen automatically in under a minute without Joe even lifting a finger? That's exactly what we're about to build. We'll create an automation that takes any new form submission, researches the contacts website, uses AI to write a personalized email and meeting notes, adds the event to a calendar, and sends the reply that feels handwritten, allowing Joe or you more time to focus on what really matters. Let's get started. Use the link on screen or in the description below to get signed up for a freemake.com account. When you click on the link, you'll land on this sign up page right here. You can click continue with Google. Click see other options to sign up with Apple, Facebook, or GitHub even or sign up with your email below. I'll go ahead and sign up with Google. You may be prompted to add some more information like your name. Go ahead and select the hosting region and country closest to you. Then click sign up for free. You also may need to complete a capture. Let's prove I am not a robot. And after sign up, you'll be taken to a welcome onboarding workflow. Go ahead and fill out the survey and then click send. Once you complete that, you'll land on the dashboard here. Welcome to Make. Now that we've got our account set up, let's set up our first automation and add a trigger. In Make, automations are called scenarios. To create your first scenario, click the button at the top of the dashboard. The first time you open up this create scenario workspace, you may get a popup like this that says you can build from scratch, start with a template, or take a short tour. We're going to build from scratch today, but we'll talk about the templates later. Go ahead and click build from scratch or click the X at the top right to close out this dialogue. And here we have a big purple plus button in the center of our screen. Now, let's set up our first trigger. A trigger is the event that causes your automation to run. If you click the plus button in the center of the screen, you can see a list of apps appear. If you scroll through, there are literally hundreds of apps. These are all apps that you can use to trigger your automation to run based on various events that take place within those apps. Today, we want to trigger our automation to run when somebody submits a contact form. There are lots of different apps you can use for your contact form, but today we're going to use Tally. I like Tally because it's free, easy to use, and makes beautiful looking forms. Plus, it integrates nicely with make.com. In the search field on the app popup, search for tally, spelled t a l y. It should be the first option that appears, a black circle with the text tally in it. There are two options that appear for triggers. We want watch new response because it has the instant tag. This means that the moment somebody submits a contact form, our automation will begin. Go ahead and select that option. And tally gets loaded in as our trigger. Immediately, there's a pop-up that appears that says create a web hook. Now, what is a web hook? A web hook is a simple way for one app to tell another app that something has happened. For example, a user might fill out a web form on one app. When the user submits that form, the web hook carries that information and delivers it instantly to the second app. In our case, that'll be the web hook receiver, which is our trigger at make.com. That will kick off our automation instantly. So, first things first, we need a web form. Go ahead and use the link that appears on screen or in the description below to get signed up for Tally. You'll land on this page here. Go ahead and follow the prompts to get signed up. When you finish the sign up process, you'll land on the tally dashboard. Click the button in the center of the screen to create a new form. Then click the use a template link. One of the first templates available is this contact form template from Marie Martins. Go ahead and click that one. Then click the blue use this template button in the upper right. Change the name to contact form or whatever else makes sense. You could say contact us, contact me, and then hover over this placeholder text and click the trash can that appears to delete this block. Do the same thing for the blank space block above the fields. Our form has the foundational fields: first name, last name, phone number, email, and a general message or question. But we want to collect a little bit more information from the people who visit the website and submit the form so that we can really personalize the response when our automation runs. So, first hover over the phone number field and click the plus button to insert a block below it. Then, scroll down and select the link field from the input blocks category section at the bottom. Then, click insert. For the placeholder text, type website or social media link. Next, hover over the your question block and click the plus button next to it. Let's allow people who are reaching out through this form to suggest a date and time for a consultation meeting. From this first section labeled questions, select date and then click insert. For the question, type something like when is your preferred meeting time. Then hover over the date field. Click the plus button to add another block. Scroll to the input block section at the bottom and select time, then insert. Click and drag the six dots to the left of the time field to the right side of the date field to put them right next to each other. If you want to, you can scroll down and customize the thank you page. Leaving this thank you page toggled on will make it so that this page two appears after the submit button is clicked. You can also customize the style by clicking customize in the upper right and then a control panel appears which allows you to get really granular with the look and style of this form. I'm going to skip that for now, though. Once you've got your contact form looking like this, go ahead and click publish in the upper right. On the next page, if you click the copy button, open up a new tab and paste in the link. You can see the contact form live on the internet. This is how it looks as a standalone page, but you can also embed this directly in your website. To do that, you'd scroll down on this share page and use the embed form options. For our demo today though, I'll just stick with the standalone page. Now that we have our web form set up, let's configure our trigger in make. Head back to your make tab and then for the tally trigger, click create a web hook. Give your web hook a name. I'll call mine tally contact form web hook. Then click create a connection. Click the drop down under connection type and select tally ooth and give your connection a name. I'll just leave it as my tally ooth connection. Click save. And a dialogue window will appear asking for authorization to connect make with tally. Go ahead and scroll down and click accept. And just like that, our tally account is now connected to make. Now we need to select our contact form. Under the form ID section in the create a web hook dialogue, select your new contact form. Then click save. And you can see here back in the original trigger configuration popup that the web form is now configured. Go ahead and click save. Now we need some data to work with from our web form. So go ahead and head back to your live tally web form and fill it out with some sample data. I'm going to go ahead and fill out this contact form on behalf of Catherine Smith. She's a professional violin player who needs some help with her website. It's a little outdated, so she needs some design work and she wants some SEO help. I'll also go ahead and fill this out with Katherine's preferred meeting time. Let's say January 7th at 100 p.m. Now, hold on. Before you click submit on this form, head back to make. At the bottom left, click the purple run once button. Now, you should see a circle with a spinning loading icon on your tally trigger. This means our trigger in make is now waiting for a new form response. return to your contact form and hit submit. We get the confirmation in tally. And if we return to make, you can now see there's a popup with a bunch of data that was pulled in from our web form. And there's a green check mark next to the name tally to show you that it worked. Now that we've got our trigger all set up and we're receiving information from the contact form in make, we need to do something with that information. Let's integrate Google Sheets so we can store that data and use it for future steps. Before we can connect Google Sheets, we need to have a spreadsheet to connect. Open up sheets.google.com in a new tab. I've left a link in the description below. In the start a new spreadsheet section, click blank spreadsheet. Where it says untitled spreadsheet in the upper left, click highlight the text. Then give your spreadsheet a name. For example, contact form submissions. Next, let's add headers to our columns so we can easily sort and review our data. Go back to make.com and in the operation popup that's open, find the output section and then go down to fields and click the plus next to it to open the fields. Next, copy all the field names and the responses in the field section. Return to Google Sheets and then in the A1 tab, paste your data. It should show up like this where you have a field name, then the response, a field name, then the response, etc. Go ahead and click command X or controlX on each of the field names and then paste them into the various columns. It should look something like this when you're done. Then highlight all the sample answers and hit delete on your keyboard to remove them. If you want to adjust the spacing of the columns so you can see the full questions and you can clear the formatting to make it more neutral by highlighting them all and automatic hitting command backslash. Finally, we want to freeze this first row to make it a header. Click view and then under freeze, select one row. When you're done prepping your spreadsheet, it should look something like this. Now, let's map our data in make. Return to and then close out this operation output panel. On the right side of the tally tricker, there's a plus button. Click that to add another module. Then select Google Sheets from the list. For actions, select add a row. Next, you'll need to connect your Google account to make. Click create a connection. Then click sign in with Google. Just like with Tally, you'll get an authorization window popup. Select your account from the list. Click continue. Then click the check box next to select all. Scroll down and click continue. Make will automatically connect to your Google account. Now let's select the spreadsheet. Under spreadsheet ID, click the blue click here to choose file button. Then select the contact form from the list. Then under sheet name, click the drop down and select sheet one. There's only one sheet in our spreadsheet so far. There's a question that says table contains headers. Leave that set to yes. And now we want to map the values. The values that appear here above the blank field are the names that we gave each of our columns. You can see first name is column A, last name is column B, phone number is column C, etc. So now we need to map the information from the contact form to show up in the correct column in the Google sheet. Click the blank field under first name and a new popup appears to the right. It says tally one watch new responses with a bunch of information below that. This is all the data that we are able to use as a result of our trigger firing. Under the fields section, find where it says first name and then click and drag first name from the panel on the right to the blank field under first name in the panel on the left. Do the same thing for all the fields from your contact form. And just for good measure, it's important when you're logging data to have clear identifiers for each data set. So let's grab the event ID from tally on the right and drag it in to a blank column on the left. Then click save. Now that we've mapped our data, let's test and make sure that Google Sheets is doing the right thing. On the bottom left, next to the run once button, there's a down arrow. Click that. and then under scenario run, click the dropown and select the last run. This allows us to run the automation with old data. So you don't have to submit a new contact form every time. Go ahead and click run once. And just like that, we get a green check mark next to tally and Google Sheets. If we click the double check mark button with the one next to it above Google Sheets, we can see the input and output bundle that were created as a result of this automation run. And if we return to our Google Sheets tab, you can see the information from our web form has now been pulled in and assigned under the correct columns. Since now we're also capturing an event ID, I'll go ahead and in our final column here, add the header event ID. So now our web form is capturing responses and we're storing the response information in a Google sheet. Next, I'll show you how to set up logic and filters so that your automation can make decisions based on the inputs coming in. Okay, take a quick look at this website. The URL in here is katherinemith violin.com. Notice anything interesting? While this is a pretty common way to share websites with other people, most of the time your browser or automation tools are going to need the full URL. For example, everything that comes before this https, that sort of thing. So, let's set up our automation to check if the URLs are properly formatted when coming in from the web form. In make, on the right side of the Google Sheets module, click the plus button to add another module. Then click flow control and then select router. A router is a module that allows us to split the automation into several paths. By default, both paths will run automatically. But you can also set up filters so that only one out of several paths runs if certain conditions are true. Let's set up our first path with a filter to only run if the URL is properly formatted. and we'll set up the second one to run if the URL is not properly formatted. To add a filter, click the wrench, then click set up a filter. Let's give this filter a label. We'll call it URL formatted correctly. Next, we need to set up a condition to evaluate. In the first blank field, click to open our input options. Scroll down a tally. Select website or social media link. Click the drop down to change the operator and then select contains case insensitive. Then we'll type http colon slash slash. Then click add or rule. This makes it so the first path will run if the first condition is true or the second condition is true. If you wanted to run this path only if both conditions were true, you would select add and rule. But in our case, what we want to do is evaluate for HTTP or HTTPS. So in the new blank field at our website, change the operator to contains case insensitive and then add https colon slash slash. Then click save. Because we only have one other path, setting up our other path is super easy. We can click the wrench, click setup filter, label it URL not formatted correctly, and then set the route as a fallback. A fallback route is the route that'll be used if the information didn't pass any other filter. So here we can just simply click save. Now before we go any further, let's save our automation so that we don't lose any progress if we need to leave or refresh the page. Click the save icon in the bottom middle. If you haven't saved in a while, it should be lit up as a light orange color and then change green once you've saved. That covers the basics of logic and filters. Next, let's set up a web scraping tool that automatically looks at the website that the contact form provides to gain insights about its contents automatically. To automatically pull information from the website provided in the contact form, we'll use a tool called Browse AI. Use the link on screen or in the description below to get signed up for free. Go ahead and follow the prompts to get signed up and then meet me on the next page. Once you create an account, you'll get this onboarding survey. Go ahead and fill that out. For the how did you hear about us drop down, click YouTube. When you get to the question that says how do you want to extract data, go ahead and click I want to do it myself but have no experience in scraping web data. All right, we're in. The first page you'll land on after signup is the build new robot page. It prompts you to select one of these options, either extracting structured data or monitoring site changes. These are fine if you want to build from the ground up, but I'll show you how to grab a pre-built robot so that you don't have to build from scratch. In the address bar of your browser, navigate to browse.ai/prebuilt-root. Here you can scroll through and find tons of pre-made web scraping robots. There's tools for WordPress, LinkedIn, Make, and tons of other tools. What we're going to use is a tool that simply extracts HTML from the website. In the search pre-built robots field, type HTML and select the robot named extract HTML code and capture a screenshot from any web page. Then click setup. Now you'll need a web page URL for testing. So I'll grab the URL from our spreadsheet and paste it in. And of course we want to make sure that it's formatted properly with the http colon slash. If you don't include that, this won't work. That's why we set up the filters earlier. Scroll down and click next step. Then review that everything looks good and click finish. This will run a test task. You can watch as browse AI navigates to that URL and pulls information from the web page. I'll fast forward to show you the results. When it's done, you should get a success message. And if you scroll down, you'll see it captured a screenshot of the website, which we can click on to see bigger. Oof. Yeah, that website needs some help. No wonder they're reaching out to Joe about web design. You can click the X in the upper right corner to close the screenshot. And to see the HTML, you can click read more. And there's the full HTML code from the site. Now, unless you know how to work with HTML code, this can look kind of intimidating, but don't worry about it. We're going to use AI to process this information. And AI knows exactly what to do with HTML. Let's go back to make. Now that we've got our robot set up in browse AI, let's set up Browse AI inside of Make. We'll need to pick one path of our automation to start with. For me, since I know that the URL in the web form is not formatted correctly, I'll start with the fallback path. Click the plus button. Search for browse AI and select run a task. Click create connection to link your account. Give your connection a name if you'd like. Then click save. Just like with the other apps, you'll get an authorization window that pops up. This one doesn't require any additional steps though if you're already logged in to Browse AI. Next, we need to pick our robot. Now, if you click in the robot field, it'll pull up our inputs list, which we don't actually want. That's because right now, make.com is set to map mode. See this toggle on the right side that says map? Toggle it off. Now, this blank field turns into a drop down, which we can click, and then select our robot, extract HTML code. Here it pulls in the webpage URL, the katherine smithviolin.com for me. But we actually want to set this dynamically. Instead of just checking this website every time, we want to check the website that comes in on our web form. So let's get rid of that URL. And then in our inputs list, select website or social media link. Then click save. Now let's test our automation to make sure it runs correctly. If our logic is set right, this fallback path should run. Click the drop down arrow next to run once. Select the most recent successful scenario run. Then click run once. Here we got an error. This happens sometimes. It's pretty normal to need to debug while you're building automation. If you ever get an error, click the red icon that appears to see the logs. Remember how I said browse AI wouldn't run unless the URL was formatted correctly? That's what this error is here. Invalid URL in parameter origin URL. Let's click close and fix this. Open browse AI and click into the webpage URL field and then move your cursor to the left of the website or social media link dynamic input. Then type http colon slash slash. Now, if the URL that's included in the contact form does not have the HTTP prefix, our automations logic will check for that and add it before it hits browse AI. Click save and then let's run a test again. Click the drop down next to run once. Again, select the most recent successful run. The last one was not, so let's choose the one before that. Then click run once. Now our automation runs correctly. And if we click the two check marks button to open our operation summary, we can see that browse AI ran and generated an output bundle. But you'll notice something here. If you click to open captured texts, it's empty. Why is that? Browse AI can take a little while to run its task. What's happening here is that make successfully starts the task, but it doesn't wait for browse to finish before continuing with the automation. In order to continue building our automation workflow, we'll actually need to set up another scenario. We can trigger the new scenario to start once browse AI finishes its task. But in order for the new scenario to know anything about what happened in this one, we need to send it some information. So, let's log some additional information in our Google sheet to help pass the form information along to the next scenario. To the right of browse AI, click the plus button to add another module. Select Google Sheets, then select update a row. Because you've already connected your Google account, it's already linked and we don't need to create a new connection. Click the blue button under spreadsheet ID to select your spreadsheet. Then select your contact form. Pick sheet one. And for row number, we'll need to update the row that we just created in Google Sheets. So, click into the blank row number field, find the Google Sheets input section, and then select row number. We'll make sure to let it know the table contains headers. And let's find a blank column. The last column that we named earlier was the event ID column, in this case, column I. So, let's put some new information in column J. Click into whatever your final empty field is and then from the browse AI input section, select task ID. The browse AI task ID is a unique identifier that gets assigned to every task. By logging this in our spreadsheet, we can pick up right where we left off in our next automation by looking up this task ID. Go ahead and click save and then return to your spreadsheet and give the final column a name. In my case, that's J. And I'll call it browse AI task ID. Let's return to make and run one more test here. Again, we'll run it with our last successful run data and run once. And if we check out our spreadsheet, you can see that there's a few duplicate entries here from all the testing we've been doing. But now our last column, browse AI task ID, includes the task ID that was generated when we started the browse AI task. Let's return to make and save our work. Let's finish setting up our URL formatted correctly path. Click the blank module and set up browse AI just like we did for the other path. But this time for the webpage URL, all you'll need to do is select website or social media link. You don't need to add the HTTP or HTTPS prefix this time because this path only runs if the URL was formatted correctly in the first place. Next, the Google Sheet module should run pretty much the exact same in either path. The only thing that really changes from path to path is what we do with the browse AI module. So, instead of clicking through and manually setting up a new Google Sheets module, let's simply copy this one. Select a module by holding shift on your keyboard and clicking the module you want to copy. Then hit command C on Mac or control C on Windows to copy. Click into a blank space and then hit commandV on Mac or controlV on Windows to paste. And just like that, the new Google Sheets module's been added. And if we drag it right next to the browse AI module, it'll connect automatically. Now, there's one small configuration change we need to make. Click the module to open it. Scroll down to the field where we're logging the task ID from browse AI. Delete that one and then select task ID from the input list on the left. The old one wouldn't have worked because it was referencing the browse AI module in the first path. We need to reference the browse AI module in this new path. This scenario is looking pretty good. Before we close out of it, let's click this magic wand icon at the bottom to auto align everything and make it look nice and pretty. Then we'll click save and we're good to go. Now we're all set to start building the next phase of our automation with our new scenario. As we build the next scenario, we'll need to do some testing. And that testing will require activating this scenario. So rightclick the scenarios menu button on the left and click open in new tab. Then click on your new tab. Then click the create scenario button in the top toolbar. Just like the first time we created a scenario, we have a big purple plus button in the center of the screen and the apps list opens up. Go ahead and search for browse AI and select watch task execution finished. In the configuration popup, click create a web hook. Select your robot from the drop down and then from the event dropown, select task finished successfully and click save. Make will set up the web hook for you. Go ahead and click save. All right, now we need to get some test data. And this is why we left the other tab open. Go ahead and click run once in the bottom left. Now, browse AI is looking for a completed task, but we need to initiate a task to have a complete one. So, go back to your first scenario and then click the drop down to run with existing data and again select the most recent successful task run. Our scenario ran successfully. So, let's return to our new scenario. Now, when you return to this new scenario, you may see a couple of different things. The first thing you may see is that the run once button turns red and starts looking for data to come in live. Or if the task finished, you'll see that now there's unprocessed data in the web hook queue. This means that the web hook received information but hasn't done anything with it. This is perfect. Let's run this scenario using existing web hook data. And there we go. Now we have some data to work with. Under the operation one output, click to open the task details with the plus button. And here we can see the task ID. If we go back to our Google sheet, we can see that the most recently logged browse AI task ID is the same ID as what just got pulled in in our new scenario. This is great. So now we need to look up this row in our new scenario. Let's return to our new scenario and make close out this operation summary and click the plus button to add a new module. Then select Google Sheets. Now we want to look up information, not add information to the Google sheet. So we'll select search rows for our action. Select your spreadsheet from the list. Select the relevant sheet table contains headers and then let's set up a filter. Click the first blank dropdown and select the browse AI task ID. Then leave text operators equal to. Click in the blank space below and select the browse AI task ID. Click save. And now let's test our new module. Click the drop down arrow next to run once. Select the most recent successful scenario run and click run once. Now, if we click to open the operation summary for Google Sheets and we scroll down to see the output bundle, we can see all the information was pulled in from that row in our Google sheet. This is the same information that we logged from the contact form. Great. So, now we're operating with all the same information that we had before. Let's go ahead and save our progress. Our automation is now logging submissions, filtering data, scraping websites, and passing everything to a second scenario. Now, let's make it smart with an AI agent that can actually make decisions, schedule meetings, and send emails for you. An AI agent is essentially an LLM with access to tools. It can actually do things for you, like scheduling events or sending an email rather than just giving you a text output. To add an AI agent in make, let's click the plus button on the right side of our Google Sheets module and then search for agent. The very first option is make AI agents and we'll select run an agent. In the settings panel that appears, click create an AI agent. Then click create a connection. Give your connection a name if you'd like and then click save. Next, give your agent a name. I'll call mine AI autoresponder. Next, select a model from the drop down. Personally, I like to use the larger models because they're smarter. Next, we need to give our agent a system prompt. A system prompt is essentially a primer message that tells our agent how to behave, what its purpose is, and if there are any guidelines it should follow when crafting a response. To make it easy to build your first system prompt, I've created a template that you can use. To use the template, click the link in the description below. I'll give you a quick rundown of this template and you can modify it to fit your own purposes. First, we have an identity. We tell the agent who it is. In this case, we're telling it that it is acting as Joe from Joe's web design. And the context is it's responding to contact form submissions and we're telling it what tools it will have access to. We're telling it what input data we're going to give it. And then we're giving it a few tasks. Task one is to evaluate and determine whether it's appropriate to schedule a meeting or not. If it is appropriate to schedule a meeting, it'll check the calendar to see if their preferred date is available and then schedule it if it is. If not, it'll find some available times to propose. Task two is to write a response. It'll analyze the provided website HTML to analyze their business and anything about them. There's also some parameters it should follow in crafting a response. Finally, task three is to send that message via Gmail to the provided email address. Go ahead and hit command A on a Mac or control A on Windows to highlight everything and then command C or control C to copy and return to make. Then paste it in for your system prompt and click save. Now quick note, we set this up using makes's built-in AI capabilities. However, you can also use other third party LLMs like OpenAI, Claude, or Gemini. I actually prefer to use the most recent model from chat GPT because I think it does a really good job as an agent, but it's a little bit more complicated to set up. So, for our tutorial today, we're keeping things simple by using makes built-in AI capabilities. Next, let's give our agent some inputs. Scroll to the bottom of the configuration panel and under messages, click add item. Click in the blank space under message one and then let's pass along all that information from our spreadsheet. For example, we'll say first name colon and then we'll click on the first name from our spreadsheet. We'll create a new line, type last name, and then add the last name from our spreadsheet. Continue until your message looks something like this. We want to include the name, the website, email, the message, the preferred date, and preferred time. Next, create a new line. Say HTML, and then let's add the HTML that was captured by our browse AI module. under the browse AI inputs. Click the arrow to the left of the captured texts section to expand it and then grab the HTML output. Once you've done that, click save. Now, let's go ahead and test our agent. Click the drop down arrow next to run once and rerun a recent successful scenario. Our agent ran successfully. And if we click to open the operation summary under output and bundle one, we can see a response item which we can expand to see the subject line and the message it created. Now, we told the agent that we gave it access to our calendar and Gmail, but we haven't actually done that yet. So, let's set up our calendar now. To connect the calendar, we're going to do something a little bit different. Instead of adding it by adding a whole new module after the make AI agent, instead we're going to give the AI agent a calendar as a tool. So click to open the agent and then in the tools section, click add tools and click module. Click the select a module tool dropdown and then click create module tool. Search for calendar and select Google calendar. Next, find get free/ busy information and select that from the list. You can change the name and description if you want, but you don't really need to. For connection, select your connected Google account and then if prompted to update the connection permissions, click continue and follow the prompts. Next, for time range from, click let the AI agent decide. And then for time range two, select let the agent decide. Finally, under calendars, click add item, change the mapping toggle to off and then click the drop down and select the calendar you want to check. Once you've done that, click add. Now our AI agent has access to check this Google calendar to see if it's free or busy on any particular date and time. Now let's give it the ability to add events to the calendar. Again click add tools module. Select the module tool and create module tool. Again select Google calendar and then select create an event. Again you can change the name and description if you want but you don't really need to. Scroll down and your connection should already be set. Change create an event from quickly to in detail. Select your relevant calendar from the calendar ID drop down. Then for event name, check let AI agent decide. For add Google meet video conferencing, check the button for yes if that's how you want to do your meetings. For attendees, select let the AI decide. All day event, we'll say no. Start date, we'll say let AI agent For end date, check let AI agent decide. Then for duration, let's set how long we want our meetings to be. Let's say 30 minutes. The format is hh col mm. So we'll say 00 col 30 to make the default duration 30 minutes. Next, check the toggle for advanced settings and scroll down. Then let's check the box to let the AI agent decide what the description should be. Since Joe of Joe's Web Design does video conferencing, a location isn't needed. We can skip that. Then go through and set the rest of the calendar settings the way you want them. These defaults work for me. So, we'll click add. Now that our AI agent has access to the calendar, let's also give it access to Gmail as a tool. In the make AI agent configuration popup, click add tools module. Select the module tool, then create module tool, and select Gmail in the app search. Then send an email. Again, you can give it a name and description. I'll just leave it as it is. Then click create a connection. Then click sign in with Google and follow the prompts. Once you're all connected, scroll down and for the two field, check the box to let the AI agent decide. Let the AI agent decide the subject. Change the body type from collection of contents to raw HTML. and then check the box to let the AI agent decide the content. Finally, click add. Now, when I click add here, it doesn't take. And if we scroll to the top, you can see why there's an error. It says maximum number of active scenarios has been exceeded in make. On the free plan, you can only have two active scenarios. Now, you might say, well, we haven't activated any scenarios yet. That's because each module inside of the AI agent counts as an active ondemand scenario. It's technically a little mini scenario that the agent can run whenever it needs to. So, in order to finish our work and save this module, we'll need to sign up for a paid account. Without closing this tab, on the left side, right click on the org button and click open link in new tab. Then, in the white menu on the left side, click subscription. Scroll down to compare plans and upgrade to at least the core plan. Once you've done that, you'll get a confirmation saying your plan was successfully changed. Great. We're now in the core plan. Let's get back to work. We'll close out this tab and then in our open ad module tool for Gmail, let's click add. And there we go. Now our AI agent has access to our calendar and it can send emails on our behalf. Click save to lock in the changes for your AI agent. And then let's save our scenario also. Now our AI agent has access to our calendar and our email, but we still need to test it. In a new tab, let's open up our calendar. And in another tab, let's open the email account for the email that was included on the contact form. I just so happen to have access to Katherine Smith's email address here. Returning to make, let's make sure that our new AI agent is working properly with all its tools. Click the drop down arrow next to run once and run a test with the data from a recent scenario run. make shows us success. But here's the moment of truth. Let's open up the calendar and we can see that a consultation has been added for January the 7th. Checking the email account. Let's refresh the inbox. And there's both an invite to the consultation event as well as an email response. Now our automation is fully built. When someone submits the contact form, they should get a personalized reply within a minute. But we've only tested this in pieces. Let's turn everything on and see if it actually works. Let's make sure our scenario is saved and then on the left side menu click scenarios. Let's turn on both of our scenarios here. On the right side next to each of them, toggle the switch. Now, theoretically, as soon as a contact form is submitted, the automation should run with the first one being our tally trigger and the second one being activated by our browse AI task completion trigger. Let's submit some information for our contact form. I'll fill it out with the same information as last time. Although this time I'll type a slightly different question and give it a different date. Once your test form is filled out, go ahead and hit submit. And after about a minute, a new event appears on our calendar. And if we click to open it, we can see the agenda is included as well as a Google Meet link. And then if we go to our inbox and click refresh, the new event invitation appears along with the corresponding personalized email. Our automation is live and working, booking meetings and sending personalized emails within moments. But when you're building on your own, you'll run into errors, and that's normal. Let's look at how to troubleshoot when things don't go as planned. If your automation doesn't run successfully, you'll get some sort of error notification. For example, here in the all scenarios view, we can see a little yellow triangle here saying the scenario requires your attention. Let's click to see more details. Here it says the reason for the error is that validation failed for one parameter. Let's click the history tab. Then let's click the details button on the last error run. Here we can see in the log that it says validation failed for one parameter and then the invalid parameter is the URL. This is for our browse AI module. So if we click the module, we can see more details of the operation. It's almost inevitable that you'll need to debug your automation at some point, but Make makes it super easy. Simply go to your history, look through the logs, find the point in your automation which has an issue, read the error message, and then update your automation accordingly. Now that you know how to troubleshoot and fix common automation issues, let's make things even easier. Why build everything from scratch when make.com has a huge library of readytouse templates? Let me show you how to jump start your next automation. From your dashboard on the left side, find and click templates from the menu. And here you'll get a massive list of readymade automations that you can grab and start working with immediately. Or instead of scrolling, you can search for apps or functions by name. For example, let's say you wanted to connect Tally with Slack. You could search for Tally, then click it in the list, and then type Slack and click it in the list. And now by using those filters, we get a personalized list of templates that use those two apps. To start using one of these pre-made automations, simply click on the one you want to use. Click on the start guided setup button and then follow the instructions provided by the light pull pop-ups throughout the configuration panels. You just learned how to automate tasks, add AI and logic, troubleshoot issues, and connect all of your favorite apps. You now have the foundation to automate anything with make.com. If you haven't already, sign up for your freemake.com account with the link in the description below. Thanks for watching.