Data syncConnectorsAutomation
Make
Start a Make scenario with each Encatch survey response - where to create the Custom webhook in Make and how to connect it
Overview
The Make connector sends each survey response to a Make scenario through a Custom webhook made in your own Make account. It works on every Make plan, Free included.
| What it gets | Each response starts a scenario |
| Events | Survey submitted, and Survey partially submitted when ticked |
| Anonymous respondents | Supported, with Include anonymous respondents on |
| Status | Available |
What You'll Need
Before you start, make sure you have:
- A Make account — any plan
- About 5 minutes
Step 1: Create the Custom webhook in Make
- In Make, create a scenario.
- Add the Webhooks app and choose Custom webhook.
- Click Create a webhook and give it a name, for example
Encatch. - Optional, recommended: turn on API Key authentication and add a key. Encatch sends it in the
x-make-apikeyheader. - Click Save. Make shows the webhook URL,
https://hook.<region>.make.com/…, and starts listening. Copy the URL.
Step 2: Add the connection in Encatch
- In Encatch, open Data sync → Survey events and click Add connection.
- Choose Make and enter a Name.
- Fill in the settings:
| Field | What to enter |
|---|---|
| Webhook URL | The Custom webhook's URL. |
| API key | Optional. The key you added under API Key authentication. |
- Pick the surveys, click Save, then press Test connection. Make shows values detected and ready to map.
Step 3: Finish the scenario and start sending
- In Make, add the next modules, save the scenario and turn it on.
- In Encatch, press Start sending.
The fields are described in the payload reference.
Good to know
- Make queues calls while the scenario is off and answers as received, so Encatch cannot tell. Check the scenario's history after Test connection.
- Make deactivates a webhook that is not attached to a scenario for 5 days.
- A full queue. If the scenario falls behind, Make's queue can fill up; Encatch retries until there is room.
- Partial responses arrive with
response.statuspartialand the answers given so far, once, when Encatch closes the response. A response is sent as partial or as submitted, never both. - Anonymous respondents arrive with
user.anonymoustrue,user.idempty anduser.anonymous_idset. - Repeats. A retry can deliver a response twice: use
event_idto skip repeats. - Rate limit. A new connection starts at 600 a minute. Make takes 300 requests per 10 seconds (1,800 a minute). Accepted requests wait in the webhook's queue, which is small on small plans.
Troubleshooting
| What Encatch shows | What it means | What to do |
|---|---|---|
| Make has no webhook at this URL | The webhook was deleted or deactivated, or the region in the URL is wrong | Open the webhook in Make and copy its URL again |
| Make refused the API key | The key differs from the webhook's API key | Enter the same key in Encatch |
| This isn't the webhook URL Make gives | Not a hook.<region>.make.com URL | Copy the URL from the Custom webhook |
Was this page helpful?
