Make Tutorial: Build Your First Workflow Step by Step

This Make tutorial builds your first workflow step by step: connect Gmail to Google Sheets, test it, schedule it, and switch it on in about fifteen minutes.

By Galactic News Editorial · Published 2026-11-09T22:29:14+00:00 · Updated 2026-11-09T22:29:14+00:00

Make tutorial showing how to build your first workflow step by step

Make Tutorial: Build Your First Workflow Step by Step

This Make tutorial builds a real workflow in about fifteen minutes. You will connect Gmail to Google Sheets so that every new email with an attachment is logged in a sheet. You need a free Make account, a Gmail account, and a Google account. No code is needed. By the end, you will know the five core Make concepts and have one working automation.

Five words to learn first

Make uses its own terms. Learn these five before you build.

The free plan includes 1,000 credits a month, two active scenarios, and a 15-minute minimum interval between runs. That is enough to learn with.

Build your first Make tutorial workflow

Follow these steps in order. Keep the Make tab open throughout.

  1. Create a free account. Go to make.com and sign up. No card is needed for the free plan. Verify your email, then open the dashboard.
  2. Create a new scenario. Click the “Create a new scenario” button in the top right. A blank canvas opens with a large plus icon in the middle.
  3. Add the trigger module. Click the plus icon. Search for Gmail and select it. Choose the “Watch Emails” trigger. This module checks your inbox for new mail.
  4. Connect Gmail. Click “Create a connection” and sign in to your Google account. Grant Make permission to read your mail. Set the trigger to watch only emails with attachments, so the scenario does not fire on every message.
  5. Add the action module. Click the small plus icon attached to the Gmail module. Search for Google Sheets and select “Add a Row”. Connect your Google account again if asked.
  6. Choose the sheet. Pick the spreadsheet and the sheet tab that will receive the log. Map the fields: sender name to one column, subject to another, and date to a third. Click a field to insert data from the Gmail module.
  7. Test with Run once. Click “Run once” at the bottom left. Make runs the scenario immediately and shows each module's input and output. Check the sheet. A new row should appear for each matching email.
  8. Set the schedule. Open the scheduling settings. The free plan checks as often as every 15 minutes. Pick an interval that fits the job. A 15-minute check uses about 96 credits a day for the trigger alone, so keep the filter tight.
  9. Save and switch on. Save the scenario, then toggle it from OFF to ON. A scenario does not run on a schedule until you switch it on. This step is easy to miss.

Test and fix common errors

Most first scenarios fail for small reasons. Check these first. A connection error usually means the Google permission expired. Reconnect the app and run again. An empty sheet row usually means a field was mapped to the wrong output. Open the Gmail module's output bundle and pick the right field. A scenario that never runs is usually still switched off. Check the toggle in the top right. A scenario that eats credits usually has a loose filter. Tighten the trigger so it fires only on the mail you need. Make shows the result of each run in the execution history. Open a failed run to see which module stopped and why.

Keep your scenarios tidy

Good habits save time later. Give every scenario a clear name that states its job, such as “Gmail attachments to Drive”. Add a short note to any module with a tricky setting. Check the execution history once a week and fix the errors you find. Delete test scenarios you no longer need, so the dashboard stays readable. These habits matter more as your library grows. A tidy workspace makes the next automation faster to build and easier to trust.

What to build next

Once the first scenario works, try a second one. Save form submissions to a sheet. Send a Slack message when a new row appears in a sheet. Post new RSS items to a channel. Each follows the same pattern: trigger, action, test, schedule, switch on. Add a filter module between trigger and action to skip unwanted items. Add a router to send different items down different paths. Routers and filters do not consume credits. When two active scenarios feel limiting, that is the sign to look at a paid plan. Core is listed at $12 a month for 10,000 credits on Make's pricing page. Check the live page for current prices.

Bottom line

One trigger, one action, one test run. That is the whole pattern. Build small, test with real data, and switch the scenario on only when the test looks right. Your second workflow will take half the time of your first.