Make.com Tutorial for Beginners: Build Your First Scenario in 10 Minutes
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.
What you will build
| Step | Module | Purpose |
|---|---|---|
| 1 | Google Forms (trigger) | Detects new form submission |
| 2 | Google Sheets (action) | Adds row with form data |
| 3 | Slack (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
- In Make, click Create a new scenario.
- Search for Google Forms and add it as the first module.
- Choose Watch New Responses (trigger).
- Click Add to connect your Google account (authorize if prompted).
- Select your form from the dropdown.
- Click Run once to pull sample data. Confirm you see at least one response in the output.
Step 2: Add Google Sheets action
- Click the + button below the Forms module.
- Search for Google Sheets and add it.
- Choose Add a Row (action).
- Connect your Google account and select your spreadsheet and sheet (tab).
- 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).
- Align column names with your form labels to avoid mapping mistakes.
Step 3: Add Slack notification
-
Click the + button below the Sheets module.
-
Search for Slack and add it.
-
Choose Create a Message (or Send a Message).
-
Connect your Slack workspace and select your channel.
-
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
- Click Run once in the bottom panel.
- Submit one test response in your Google Form.
- Wait a few seconds (or trigger the scenario again if using manual run).
- Verify:
- A new row appears in your Google Sheet.
- A message appears in your Slack channel.
- 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
- After successful test, toggle the scenario On (top-right).
- On the free plan, the minimum interval is 15 minutes. Make will check for new responses on that schedule.
- Re-check run history after your first real submissions to confirm stability.
Common beginner mistakes
| Mistake | Fix |
|---|---|
| Wrong mapping key | Use the field picker; select from the previous module's output |
| Connection expired | Reconnect the app in module settings |
| Duplicate rows | Add a filter or unique key check before the Sheets write |
| No Slack notification | Verify 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.
Duplicate this scenario and swap Google Forms for another trigger (webhook, email, CRM event) to practice. Start building in Make →
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.




