Step 1
In Make.com, create a new scenario. Add a Webhook → Custom webhook module as the first step. Make generates a unique URL.
Integration · Make
Send form submissions to Make to trigger scenarios.

splitforms connects your forms to Make and moves every submission across the moment it's received — no manual export, no copy-paste.
Every submission is emailed to you and saved to a searchable dashboard, so the lead is captured even if Make is unreachable.
Connecting Make to your forms is included in your plan — no add-on charge and no per-message billing from splitforms.
Example: form markup
The form posts to https://splitforms.com/api/submit. The Make routing is configured in the splitforms dashboard against the form's access key — there's no client-side Make-specific code in your HTML.
<form action="https://splitforms.com/api/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_SPLITFORMS_KEY" />
<input type="email" name="email" placeholder="[email protected]" required />
<textarea name="message" placeholder="Your message" required></textarea>
<button type="submit">Send to Make</button>
</form>How it works
Here's how to send form submissions to Make in 6 steps — no code required, and most teams finish in a couple of minutes.
In Make.com, create a new scenario. Add a Webhook → Custom webhook module as the first step. Make generates a unique URL.
Copy that URL and paste it into the form's Webhooks tab in splitforms.
Submit a test entry. The Make webhook module will receive a sample payload — Make uses it to derive the data structure for downstream modules.
Add scenario modules — Google Sheets, Notion, HubSpot, Slack, anything in Make's library — and map splitforms fields into each.
Turn the scenario on. Each splitforms submission triggers a scenario run immediately.
Optional: use Make's filter modules to branch on submission content (e.g. priority, country, source) before fanning out to different downstream apps.
How teams use it
Use Make's Webhook module as a scenario trigger and splitforms can fan out to any of Make's 1,500+ app modules. Cheaper per operation than Zapier, and the scenario starts the moment splitforms POSTs the submission. Prefer a plainer destination? The same form can also send form submissions to email or forward them to any webhook.

Why splitforms
Make undercuts Zapier on per-task pricing — both work natively with splitforms webhooks. splitforms is free for 500 submissions (no card), then $5/mo on Pro (5,000/month) or $49/year on Annual (15,000/month), with no per-integration add-on fees.

How SplitForms works
splitforms receives the submission, filters spam, saves it to your dashboard and emails you — then, on paid plans, sends it on to your webhooks and integrations. No backend infrastructure to build.

Point your form to your unique SplitForms endpoint. That's it.

We instantly capture and organize every submission in your inbox.

Send data to email, spreadsheets, CRMs, webhooks, and 7,000+ apps.

No credit card required. Set up in under 60 seconds.
Connect & automate
On paid plans, submissions can also go to Slack, Discord, Google Sheets, Notion, Airtable, Zapier or any signed webhook — and splitforms works on the platforms you build on, from WordPress and Shopify to Next.js. With Stripe connected, your forms can take payments too.

Common questions
For splitforms webhooks they are comparable. Make's Custom webhook module starts a scenario as soon as the URL receives a request (when the scenario is set to run immediately), and Zapier's Catch Hook trigger is also instant. The bigger difference is price per operation and control flow, not latency.
Make's free plan includes 1,000 ops/month with up to 2 active scenarios. Their paid plans start at around $9/mo for 10,000 ops, which is materially cheaper per task than Zapier. Pricing changes — check make.com/en/pricing for current numbers.
Zapier has the wider app library and a friendlier UI for non-technical users. Make has stronger control flow (loops, error handlers, routers) and is cheaper at volume. If you're shipping a complex multi-step workflow, Make's interface scales better. For simple two-step Zaps, either works.
Yes — splitforms supports multiple webhook URLs per form. You can fire both a Make scenario and a Zapier zap from the same submission, though for most teams that's overkill.
The submission lands in the splitforms email + dashboard regardless of webhook outcome, so the lead is never lost. A network error, timeout, or 5xx gets one automatic retry, and every delivery is kept in the webhook's delivery log for 30 days with its status, error and attempt count, so you can spot a broken scenario, fix it, and replay what it missed.
There's no reason to. Both platforms accept generic webhook triggers — splitforms posts directly to Make. Adding Zapier in between just costs extra tasks.
Simple pricing
Free gives you 500 submissions for $0 — no card, no time limit. Pro is $5/month for 5,000 submissions a month, and Annual is $49/year for 15,000 a month with every Pro feature.
For side projects and indie devs.
Every paid feature, for agencies and growing products.
Every Pro feature with triple the volume — $0.27 per 1,000 at full use.
No credit card required on Free • Cancel anytime • Full pricing and FAQ