Connecting a Form to Make (formerly Integromat)

ChargeForms doesn't have a native Make integration yet — see the Integrations page for what's on the roadmap — but its generic webhook (documented in full at Webhooks) connects to Make directly, since Make can receive and parse any incoming webhook without you writing code on either end.

1. Create a Make scenario with a webhook trigger

In Make, create a new scenario and add Webhooks → Custom webhook as the trigger module. Click Add, name it (e.g., "ChargeForms submissions"), and Make will generate a unique webhook URL — copy it.

2. Point ChargeForms at that URL

In WordPress, go to ChargeForms → Integrations and paste the Make webhook URL into the webhook field. This sets it as the site-wide default, firing for every form's submissions — if you only want one specific form to send to Make, set the URL on that form's own Settings screen instead, which overrides the site-wide default just for that form.

3. Trigger a test submission

Submit the form once (test data is fine). Make's webhook module listens for the first real request to auto-detect the data structure — back in Make, click Run once on the scenario before submitting, so it's actively listening when the request arrives.

The payload is a JSON body containing the form ID, submission timestamp, and every submitted field keyed by field ID — Make will show you this structure automatically once it captures the test request, and you can map any of those fields into the next module in your scenario.

4. Build the rest of the scenario

From here it's standard Make scenario-building — common patterns:

• Add a row to a Google Sheet for every submission, without touching the WordPress admin.
• Send a Slack message to a specific channel when a high-value payment form is submitted.
• Create a record in a CRM (HubSpot, Airtable, Notion) from the submitted fields.
• Conditionally branch the scenario based on a specific field value — e.g., route submissions differently based on which service was selected in a conditional logic form.

Handling failures

A webhook delivery failure on the ChargeForms side (Make unreachable, timeout) never blocks the submission itself — the entry is always saved in ChargeForms first, and the webhook is a best-effort side effect. Turn on Global Settings → Integration Failure Notices to get an admin email if a delivery to Make fails, so a dropped automation doesn't fail silently while entries keep coming in normally.