Make.com (formerly Integromat) sits in an interesting position in the automation market. It is more powerful than Zapier for complex logic and branching scenarios, and more accessible than n8n for teams without dedicated technical resources. If you have a workflow with multiple conditions or data transformations, Make is often the right starting point.
This guide walks through building a real automation: notifying your team in Slack when a new form submission arrives, with data formatted before the notification sends.
What You Need Before You Start
A Make.com account (the free tier works for this example), a Typeform or Google Form account, a Slack workspace, and about 45 minutes. No prior automation experience required.
Step 1: Create a New Scenario
In Make, automations are called “scenarios.” Create a new scenario and select your trigger — the event that starts the automation. Select Typeform as the trigger app and “Watch Responses” as the trigger event. Connect your Typeform account using Make’s OAuth flow, then select the form you want to monitor.
Step 2: Add a Data Transformer Module
Between the trigger and the Slack notification, add a “Tools” module and select “Set Multiple Variables.” This formats the data before it reaches Slack. Map the form fields to clean variable names: full_name, email, company, message. This step makes the Slack message readable rather than filled with Typeform’s internal field IDs.
Step 3: Add the Slack Notification
Add a Slack module and select “Create a Message.” Connect your Slack workspace and choose the notification channel. Build the message using the variables from Step 2:
New inquiry from {{full_name}} | Company: {{company}} | Email: {{email}} | Message: {{message}}
Step 4: Test the Scenario
Make has a “Run once” button that processes one existing submission to test the flow. Submit a test response to your Typeform first, then click Run once. If everything is connected correctly, you will see the data flow through each module and a Slack message appear.
Step 5: Activate and Schedule
Once tested, activate the scenario and set it to run continuously using the “Immediately as data arrives” option. Make will poll Typeform every few minutes for new submissions.
Common Mistakes
- Not testing with real data first. Make’s test mode uses the most recent submission. Submit a test entry before testing the scenario.
- Mapping fields before the form is finalised. If form fields change after you build the scenario, the mappings break. Build automations after the form is stable.
- Forgetting error handling. For production automations, add an error handler on each module. Make lets you route errors to a notification so you know when something breaks.
For more complex automations — multi-step workflows, database integrations, enterprise tool connections — WizQuest’s automation team builds and maintains these at scale. Talk to us here.