You’ve probably seen Make.com mentioned in automation discussions. Maybe someone on a forum described it as a way to connect their email to their spreadsheet to their social media without writing a single line of code. Sounds useful. But the official documentation assumes you already know what you’re doing.
Here’s the reality: Make.com (formerly Integromat) is a visual automation tool that connects over 20,000 apps. Setting up your first workflow can take anywhere from 10 minutes to several hours depending on complexity. This guide covers the actual steps, realistic costs, and where people typically get stuck.
What is Make.com and why do people use it?
Make.com is a no-code automation platform. You build “scenarios” (workflows) using a drag-and-drop visual editor. Each scenario starts with a trigger (something happens) and adds actions (something else happens automatically).
Common use cases from actual users on the Make.com community:
The platform connects tools like Gmail, Slack, Google Sheets, WordPress, OpenAI, and thousands of others without requiring any programming knowledge.
Step 1: Create your Make.com account
Go to make.com and sign up. You can register with email, Google, or Apple. The free tier gives you 1,000 operations per month—enough to test basic workflows without spending money.
Output at this stage: Active account with access to the dashboard and scenario editor.
Step 2: Understand the dashboard layout
The main areas you’ll use:
- Scenarios – where your workflows live
- Templates – pre-built workflows you can copy and modify
- Connections – where you authorize apps to talk to Make.com
Spend two minutes clicking around. Don’t build anything yet—just get familiar with where things are.
Step 3: Start with a template (recommended for beginners)
Don’t start from scratch. Click Templates and search for something relevant to your goal. Templates like “Add new Typeform responses to a Google Sheets spreadsheet” or “Post new Instagram photos to Twitter” show you the structure of a working scenario.
Using a template reduces your setup time from potentially hours to around 10-30 minutes.
Step 4: Create a new scenario from scratch
If you’re building custom:
- Click Create a scenario in the top left
- Click the central + icon to add your first app
- Search for your trigger app (e.g., “Gmail”, “Google Forms”, “WordPress”)
- Click Authorize and log into that app to grant permission
Common issue: Authorization pop-ups sometimes get blocked by browsers. If the authorization window doesn’t appear, check your browser’s popup blocker and allow make.com.
Step 5: Configure your trigger
The trigger determines when your scenario runs. Common trigger types:
- Watch Events – runs when something new is created
- Search Records – checks for something existing
- Scheduled – runs at intervals you set (hourly, daily, etc.)
Select your trigger type, configure any filters (e.g., “only if field X equals Y”), and click OK.
Step 6: Add action modules
Click the + after your trigger module to add an action. Actions are what happens after the trigger fires. Configure each module:
- Select the app (e.g., “Slack”)
- Select the action (e.g., “Send a message”)
- Map fields from your trigger data (e.g., use the email subject as your Slack message)
You can add multiple actions, use filters to add conditions, and use routers to split into parallel paths.
Step 7: Test your scenario
Click Run once to test. Make.com will execute the scenario with real data (or dummy data if you set it up). Watch the module bubbles light up in sequence.
What to look for:
- Green checkmarks = success
- Yellow warnings = data mapping issues (still works but check field mappings)
- Red errors = something failed
Testing typically takes 5-15 minutes for basic scenarios. Complex workflows with multiple branches can take 2-8 hours to fully test.
Step 8: Activate and schedule
When tests pass, toggle the scenario ON. Set your schedule:
- Real time – instant execution when trigger fires
- Scheduled – runs at set intervals (minimum 15 minutes between runs on free tier)
Step 9: Handle errors before they handle you
This is where most beginners give up. Make.com’s error handling has quirks:
- API rate limits (429 errors) – services like OpenAI limit how many requests you can make. Build in delays or reduce frequency.
- Connection failures – sometimes a connection just stops working. Re-authorize the app.
- Scenarios auto-disable – if a scenario fails 3 times in a row, Make.com disables it. Add Break error handlers to prevent this.
- Notification overload – error emails go to all team members. Check who has access to your Make.com workspace.
Set aside 30 minutes weekly for maintenance. Check your scenario history, re-test after service updates, and monitor operation counts.
Step 10: Calculate your actual costs
| Plan | Operations/Month | Approximate Cost |
|---|---|---|
| Free | 1,000 | £0 |
| Starter | 10,000 | ~£9/month |
| Pro | 100,000 | ~£26/month |
| Team | 500,000 | ~£66/month |
Operations = each time a module runs. A scenario with 3 modules = 3 operations per trigger. Most basic automations for side income work stay under 10,000 operations/month.
Make.com (free to start) costs nothing until you need more than 1,000 operations. For basic lead generation or content distribution workflows, the Starter plan around £9/month covers most needs.
Realistic timeline: when will this work?
- Basic automation (e.g., form → spreadsheet → email): 10-30 minutes build time
- Medium complexity (e.g., form → AI processing → social posting): 1-4 hours build time
- Full testing and debugging: Add another 2-8 hours, especially if you hit API errors or data mapping issues
- Ongoing maintenance: 30-60 minutes per week
From the Make.com community forums, users report building functional workflows within a day for standard use cases. Teams have published automated content systems within one week using Make.com and templates.
But expectations matter. If you’re connecting three apps, you might be done today. If you’re building a multi-step content pipeline with AI generation and social distribution, budget a full weekend.
Who Make.com is for, and who it isn’t
Good fit if:
- You want to connect tools you already use without coding
- You’re comfortable following visual step-by-step instructions
- You have a specific repetitive task you want to automate
- You’re building a side income system and need to connect AI tools to your workflow
Not for you if:
- You need instant results without testing – plan for at least a few hours minimum
- You want fully hands-off automation that never needs monitoring – all workflows need occasional maintenance
- You need to process thousands of records daily on a tight budget (consider higher-tier plans or Zapier for that scale)
- You find visual interfaces confusing and prefer written scripts
Next steps
If Make.com sounds like the right fit, start with their official how-to guides and copy a template that matches your goal. Don’t try to build something unique on day one.
Check out a detailed monthly blueprint to now start building automations.
The platform has a learning curve, but it’s gentler than alternatives that require any programming knowledge. For connecting AI tools to your side income workflow without code, it’s one of the most flexible options available.
Set realistic expectations: budget 2-4 hours for your first meaningful automation, test thoroughly before activating, and check your scenario logs weekly. That’s not passive income on day one. But it is building infrastructure that can run while you focus elsewhere.