Make

See the installation steps to learn how to install our app and change the form name

Trigger a Make scenario when someone submits a form on your Webflow site.

Before you start

• A Make scenario starting with the Webhooks → Custom webhook module. Copy the URL it gives you.
• The URL Make gives you is https://, which is required: plain http:// URLs are refused when you save the connection. Anything other than a 2xx response is tried again, up to 3 attempts in total, then logged as failed so you can replay it.
• Optional: add an API key to the connection and FormRelay sends it as Authorization: Bearer <key>. Most catch hooks need none.
• No field mapping is needed here — the whole submission is sent as JSON, and you pick fields apart inside Make.

Leave the Make webhook listening ("Determine data structure") while you send one test submission, so Make learns the payload shape.

1. In your App Dashboard, go to the Sites menu and click on your Authorized Webflow Site.

• Here you will see all your forms across the site.
• A form can send to several destinations, but only one of each kind. Adding a second Make destination to the same form is not possible; edit the existing one instead.

2. From the left-hand menu, click on Integrations. You will see available categories such as:
   • Apps & Platforms (Notion, Slack, Discord, Airtable)
   • Email & marketing (HubSpot, Mailchimp, Klaviyo, Brevo, MailerLite, EmailOctopus, Moosend, Omnisend, Sender)
   • Automation & Webhooks (Webhook, Zapier, Make)

3. Under Automation & webhooks, click on Make.
   • Give the connection a recognizable name (e.g., “Make — Lead capture”).
   • Paste your Webhook URL — your Make custom webhook URL (e.g. https://hook.eu1.make.com/...).
     (For details, see section 4: How to get your Make Webhook URL).
   • click "Save".
   • After clicking "Save", your added Make integration will appear under "CONNECTIONS".
   • You can edit or delete the connection at any time.

4. How to get your Make Webhook URL.
   • Go to your "Make Dashboard", you can either create your own account with a subscription or test the free version.
   • In there click "+ Create scenario" and give the scenario a recognizable name.
   • Click the "+" icon to add the first module.
   • Search for and select Webhooks, then choose Custom webhook.
   • Click Create a webhook (or Add) to generate your unique webhook URL.
   • Copy the URL shown in the module (e.g. https://hook.eu1.make.com/...).
   • Paste it into the Webhook URL field in the FormRelay app -> Integrations -> Make.
   • Keep the scenario editor open (do not activate yet) — you will send a test submission from your Form to complete the scenario setup.

5. Go back to the Forms menu.
   • Choose a Form from your authorized Webflow site.
   • Click "+ Add destination".
   • A popup will open with a dropdown for Integration → Pick an integration.
   • Select your Make integration from the dropdown.
   • There is nothing to map: the whole submission is sent as JSON, with the field names Webflow uses.
   • Click Save when finished.

6. Test the integration:
   • Go to your published Webflow site.
   • Fill out and submit the form.
   • You will see the data appear in your Make Dashboard within a few seconds.

✅ Your Make integration is now successfully set up and ready to sync form submissions.

Payload reference

Live form submission (sent on every real submit):

{
    "event": "form_submission",
    "formId": "<webflow-form-id>",
    "payload": {
        "Name": "Jane Doe",
        "Email": "jane@example.com",
        "siteId": "<webflow-site-id>",
        "formId": "<webflow-form-id>"
    }
}

• Sent as POST with Content-Type: application/json.
• Field keys in payload use Webflow field display names.

The play icon on the saved connection sends a test payload (the same shape as the Webhook test payload, with the header x-formrelay-test: 1). That is enough for Make to learn the field names; a real submission from your published site works too.

Troubleshooting

Still stuck?

Open the site's Logs page in FormRelay. Every attempt is recorded with the destination's own error message, and you can Replay a failed delivery once the cause is fixed. Delivery & Retries explains what the statuses mean.