Mastering Make.com Automations
Introduction to Make.com
What is Make.com?
Make.com is a tool that lets you connect different apps and automate tasks without writing a single line of code. Think of it like a set of digital LEGOs for your software. You can snap together different services, like Gmail, Google Sheets, and Slack, to create a custom workflow that runs automatically.
The whole point is to hand off your repetitive, manual tasks to a system that can do them for you. Instead of downloading an email attachment and uploading it to cloud storage yourself, you can build an automation that does it instantly. It's a visual platform, which means you see your workflow as a diagram, making it easy to understand and change.
With Make’s visual drag-and-drop interface, anyone can build workflows - no technical skills needed.
Your First Look
When you first log in to Make.com, you'll land on your main dashboard. This is your command center. On the left side, you'll see a navigation menu with a few key areas you'll use often:
- Dashboard: Your home base, showing an overview of your activity and scenario usage.
- Scenarios: This is where all your automations live. You'll come here to create new ones or edit existing workflows.
- Templates: A library of pre-built scenarios you can use as a starting point for common tasks.
- Connections: Where you manage the links to your different apps, like authorizing Make.com to access your Google or Slack account.
Scenarios and Modules
To build anything in Make.com, you need to understand two core concepts: scenarios and modules. A scenario is the complete automation, from start to finish. Think of it as a recipe.
Scenario
noun
An entire automated workflow that connects multiple apps to perform a series of tasks. It's triggered by a specific event and executes a sequence of actions.
If a scenario is the recipe, then modules are the individual ingredients and steps. Each module is a bubble in your scenario that performs a single action in a specific app. One module might watch for a new email in Gmail. The next might extract an attachment. A third could upload that file to Dropbox. You connect these modules to build out the full recipe.
Module
noun
A single step within a scenario. Each module performs a specific action, such as watching for new data (a trigger) or creating or updating data (an action).
The Visual Builder
The magic happens in the visual workflow builder, also called the scenario editor. It’s a blank canvas where you bring your automation ideas to life.
Building a workflow is straightforward:
- Start with a trigger. You begin by adding your first module. This is almost always a trigger, which is a module that watches for a specific event, like a new message in Slack or a new row added to a spreadsheet. This event kicks off your scenario.
- Add action modules. Next, you add more modules to perform the tasks you want to automate. You can search through thousands of apps and actions.
- Connect the dots. You link modules together by dragging a line from one to the next. This tells Make.com the order of operations and how data should flow from one step to another.
As you build, you're creating a flowchart that shows exactly what your automation does. You can see the path your data will take, making it easy to spot issues or find places to add more steps.
For example, a simple scenario could be: (1) Trigger: Watch for new emails with 'invoice' in the subject line. (2) Action: Download the attachment. (3) Action: Upload the attachment to a specific Google Drive folder.
Now you know the basic pieces of Make.com. You have scenarios that hold your workflows and modules that perform the actions. It all comes together in the visual builder.
In Make.com, what is a "scenario"?
If a scenario is the entire recipe for an automation, what is a "module"?
