Welcome to Encatch Docs
Data syncBetaConnectorsAutomation

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 getsEach response starts a scenario
EventsSurvey submitted, and Survey partially submitted when ticked
Anonymous respondentsSupported, with Include anonymous respondents on
StatusAvailable

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

  1. In Make, create a scenario.
  2. Add the Webhooks app and choose Custom webhook.
  3. Click Create a webhook and give it a name, for example Encatch.
  4. Optional, recommended: turn on API Key authentication and add a key. Encatch sends it in the x-make-apikey header.
  5. 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

  1. In Encatch, open Data sync → Survey events and click Add connection.
  2. Choose Make and enter a Name.
  3. Fill in the settings:
FieldWhat to enter
Webhook URLThe Custom webhook's URL.
API keyOptional. The key you added under API Key authentication.
  1. 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

  1. In Make, add the next modules, save the scenario and turn it on.
  2. 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.status partial and 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.anonymous true, user.id empty and user.anonymous_id set.
  • Repeats. A retry can deliver a response twice: use event_id to 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 showsWhat it meansWhat to do
Make has no webhook at this URLThe webhook was deleted or deactivated, or the region in the URL is wrongOpen the webhook in Make and copy its URL again
Make refused the API keyThe key differs from the webhook's API keyEnter the same key in Encatch
This isn't the webhook URL Make givesNot a hook.<region>.make.com URLCopy the URL from the Custom webhook

Was this page helpful?