Skip to main content

Make.com Tutorial for Beginners: Build Your First Scenario in 10 Minutes

· 5 min read
Yassine El Haddad
Software Developer & Automation Specialist

I build production AI agents, web scrapers, and automation pipelines. Most of what I publish here comes from the actual problems they run into: proxies that get banned, anti-bot stacks that fingerprint your client, RAG that drifts when the underlying data moves. Stack: Python, TypeScript, Go, FastAPI, LangChain, Crawlee, Playwright, deployed on AWS, GCP, and Cloudflare.

The fastest way to learn Make is to build one workflow end-to-end. This tutorial walks through a form-to-sheet-to-Slack automation: when someone submits a Google Form, the response goes to Google Sheets and triggers a Slack alert. You will learn triggers, actions, and data mapping.

Get started with Make.

What you will build

StepModulePurpose
1Google Forms (trigger)Detects new form submission
2Google Sheets (action)Adds row with form data
3Slack (action)Sends notification to team channel

Before you begin

You need:

  • A Make account (free tier works)
  • One Google Form with fields (e.g., name, email, message)
  • One Google Sheet with matching column headers
  • One Slack workspace and channel

Step 1: Create a new scenario

  1. In Make, click Create a new scenario.
  2. Search for Google Forms and add it as the first module.
  3. Choose Watch New Responses (trigger).
  4. Click Add to connect your Google account (authorize if prompted).
  5. Select your form from the dropdown.
  6. Click Run once to pull sample data. Confirm you see at least one response in the output.

Step 2: Add Google Sheets action

  1. Click the + button below the Forms module.
  2. Search for Google Sheets and add it.
  3. Choose Add a Row (action).
  4. Connect your Google account and select your spreadsheet and sheet (tab).
  5. Map each form field to a column:
    • Click in each "Map" field.
    • Use the picker to select values from the Google Forms module output (e.g., Response - Name, Response - Email).
  6. Align column names with your form labels to avoid mapping mistakes.

Step 3: Add Slack notification

  1. Click the + button below the Sheets module.

  2. Search for Slack and add it.

  3. Choose Create a Message (or Send a Message).

  4. Connect your Slack workspace and select your channel.

  5. Compose the message with dynamic fields. Example:

    New lead: {{1.Response - Name}} | {{1.Response - Email}} | {{1.Response - Message}}

    The {{1.}} prefix refers to the first module's output.

Step 4: Test the scenario

  1. Click Run once in the bottom panel.
  2. Submit one test response in your Google Form.
  3. Wait a few seconds (or trigger the scenario again if using manual run).
  4. Verify:
    • A new row appears in your Google Sheet.
    • A message appears in your Slack channel.
  5. If a step fails, open the failed module and check the error. Common fix: remap fields using the output picker.

Step 5: Activate and schedule

  1. After successful test, toggle the scenario On (top-right).
  2. On the free plan, the minimum interval is 15 minutes. Make will check for new responses on that schedule.
  3. Re-check run history after your first real submissions to confirm stability.

Common beginner mistakes

MistakeFix
Wrong mapping keyUse the field picker; select from the previous module's output
Connection expiredReconnect the app in module settings
Duplicate rowsAdd a filter or unique key check before the Sheets write
No Slack notificationVerify channel permissions and that the scenario ran

Upgrade path

Once this works, add one improvement at a time:

  • Filter: Only process qualified responses (e.g., valid email).
  • Router: Split high-priority vs normal leads.
  • CRM: Push qualified leads to HubSpot or Salesforce.
  • AI: Add an AI module to summarize long free-text responses.

For web data in the same flow, add the Apify integration and process scraper output with iterators.

Compliance note

Even beginner automations can process personal data. Collect only fields you need. Add retention rules. Respect regional consent (e.g., GDPR) in forms. Avoid sending sensitive data to broad Slack channels.

Next step

Duplicate this scenario and swap Google Forms for another trigger (webhook, email, CRM event) to practice. Start building in Make →

Apify Affiliate Banner 728x90Apify Affiliate Banner 728x90Apify Affiliate Banner 300x50Apify Affiliate Banner 300x50
Frequently Asked Questions

Most beginners build a first working scenario in under an hour. Depth comes from repeated practice with real workflows.

No. Most workflows are built visually. Make Code (JavaScript/Python) is optional for advanced logic.

Yes. Connect scraper outputs via Apify integration and route results to Sheets, CRM, or Slack.

Check the execution log for the failed module. Common causes: mapping errors, expired connections, or invalid data. Fix and rerun.

Common mistakes and fixes

Wrong mapping key or missing data in destination

Click the field picker in each action module and select from the previous module's output. Run the previous module once to populate sample data.

Connection expired or authentication error

Reconnect the app (Google, Slack, etc.) in the module connection settings. Tokens can expire or be revoked.