Connect Make.com via Webhooks

Use Formsuite's Webhooks feature to fire scenarios in Make.com whenever a form is submitted or a contact is updated. This is the fastest way to plug Formsuite into the 1,500+ apps Make supports, and no special Make app is required. You just use Make's built-in Custom webhook module.

How it works

1. You create a Custom webhook scenario in Make. Make gives you a unique URL.
2. You paste that URL into a new webhook in Formsuite.
3. You send a test from Formsuite. Make picks it up and auto-detects the JSON structure so every field becomes a variable you can map.
4. From there, build the rest of your scenario. Add a Google Sheets row, send a Slack message, create a HubSpot deal, anything Make supports.

Before you start

• You'll need a Make.com account (the free tier works fine for testing).
• Webhooks are a Formsuite paid plan feature.

Step 1: Create a Custom webhook in Make

1. In Make, click Create a new scenario.
2. Click the first module placeholder and search for Webhooks.
3. Pick Custom webhook as the trigger.
4. Click Add to create a new webhook. Give it a name like "Formsuite responses" and click Save.
5. Make shows you a URL like https://hook.eu1.make.com/abc123.... Copy it.

Leave the scenario tab open. Make will be listening for the first request.

Step 2: Add the webhook in Formsuite

1. In Formsuite, open Settings → Webhooks from the workspace sidebar (or click the Webhooks tile on any form's Connect page).
2. Click + New webhook.
3. Fill in:
   • Name: e.g. "Make scenario - Customer onboarding"
   • Endpoint URL: paste the URL Make gave you
   • Scope: leave empty for all forms, or pick the specific forms you want this scenario to fire on
   • Events: tick at least Form response completed
4. Click Create webhook. Copy the signing secret and stash it somewhere safe (most Make scenarios don't need to verify the signature, but it's good to have in case you ever want to).

Step 3: Send a test so Make can map the fields

1. In Formsuite, find your new webhook in the list and open the actions menu (three dots).
2. Click Send test. Formsuite fires a synthetic payload to Make.
3. Switch back to Make. Your Custom webhook module should show Successfully determined.
4. Click the module and pick Re-determine data structure if you want to refresh it later. Every field in the payload is now available as a variable: data.responseId, data.contact.email, data.answers[], data.score, and so on.

Step 4: Build the rest of your scenario

This is where Make shines. Add additional modules to do whatever you need:

• Google Sheets → Add a row: log every response to a sheet
• Slack → Create a message: notify your team about high-score leads
• HubSpot / Pipedrive / Salesforce: create or update contacts
• Airtable, Notion, Monday: push structured data into your work tools
• Email by Make / Gmail: send a custom follow-up email

Map fields from the webhook payload to the destination module's inputs.

Step 5: Turn on the scenario

When you're happy with the scenario in Make:

1. Click Save in the scenario editor.
2. Toggle the scenario ON at the bottom left of the canvas.

That's it. Every time a form fires the events you subscribed to, Formsuite will deliver a webhook to Make and your scenario will run.

Tips

• Use filters in Make to route different forms to different actions. Each payload includes formId and data.formName, so you can branch on those.
• Keep one scenario per use case. If you want both a Slack alert and a Sheet row, two separate scenarios with the same webhook trigger usually beat one giant scenario.
• Failed deliveries auto-retry once. If your Make scenario is paused or has a bug, Formsuite will retry the delivery 30 seconds after the first failure. After 10 consecutive failed deliveries we auto-disable the webhook so it doesn't keep hammering Make, email the workspace owner, and add an in-app notification. Re-enable from Formsuite after you've fixed the scenario.
• Inspect deliveries from the actions menu on your webhook row. You'll see the HTTP status Make returned and (for failures) the response body, which is usually enough to debug. Failed deliveries also have a replay button so you can re-fire them after a fix.

Troubleshooting

• Make isn't picking up the test payload. Make sure the scenario is open in the editor and the Custom webhook module is the first/trigger module. Then try Send test from Formsuite again.
• Some fields are missing in Make. Re-determine the data structure on the Custom webhook module. Make caches the shape of the first payload it sees, so if you changed events (e.g. added contact fields) you'll need to refresh.
• Webhook auto-disabled in Formsuite. Means we hit 10 consecutive failures. Check that your Make scenario is ON and your account hasn't run out of operations. Re-enable the webhook from the actions menu.

Next steps

If you'd rather use Zapier instead of Make, see the Zapier Integration article. For the full reference on Formsuite's webhook payload shape, signing, and retry behaviour, see the Webhooks article.