Make

Start a Make scenario with each new response, then send it anywhere Make reaches. Formerie sends a webhook, and Make’s Custom webhook module catches it.

We wrote this guide from Make’s documentation, and haven’t run it on a real Make account yet. Tell us if a step differs.

Connect your form

1. In Make, create a scenario, and add Webhooks, then Custom webhook.
2. Next to Webhook, choose Add, give it a name, and choose Save. Make shows the address, and starts listening.
3. In Formerie, open your form, then Delivery, and add a webhook with that address.
4. In Formerie, choose Send test. Make learns the fields from it.
5. Add your next module, and map the answers from data, then fields.
6. Turn the scenario on.

If you add a field to your form later, choose Detect new values in Make, and choose Send test again.

Make answers 200 when a request joins its queue, and 400 when the queue is full. Formerie tries a 400 again, so nothing is lost while a queue drains.

The test has test set to true, and real responses have it false. To keep test sends out of your other apps, add a filter on that value after the webhook.

About the signature

The Make address is what protects you: keep it private. Anyone who has it could send your scenario fake responses. Formerie shows only the start of it after saving, and keeps it encrypted.

To check the signature in Make, edit the webhook, and under Advanced settings, turn on Get request headers and JSON pass-through. That gives you the headers and the raw body. We haven’t tried the steps after that, so if you need the check, use your own server with the samples.

If it doesn’t work

• Formerie shows a failed try with status 400: Make’s queue is full, or the scenario is off. Turn it on or let it drain. Retries carry on.
• The webhook pauses: Formerie pauses it after 3 failed deliveries in a row. Fix the scenario, choose Resume, and what waited is sent.

Next: send responses to Google Sheets or HubSpot.