INTEGRATION · AUTOMATION

Send Form Submissions to Make — splitforms

Trigger Make.com (Integromat) scenarios from form submissions.

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-task than Zapier and runs scenarios immediately rather than polling.

Delivery mode: Native (auto-detected webhook)

Connect Make in 60 seconds See setup steps

Free for 1,000 submissions/month. No credit card required.

How to set up Make with splitforms

6 steps. The whole flow typically takes 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.

example: form markup

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_SPLITFORMS_KEY" />
  <input type="hidden" name="_route" value="make" />
  <input type="email" name="email" placeholder="you@example.com" required />
  <textarea name="message" placeholder="Your message" required></textarea>
  <button type="submit">Send to Make</button>
</form>

The form posts to https://splitforms.com/api/submit. The Makerouting is configured in the splitforms dashboard against the form's access key — there's no client-side Make-specific code in your HTML.

Who uses splitforms + Make

A handful of patterns we've seen in the wild.

USE CASE 01Routing high-volume form submissions cheaper than Zapier — Make's per-task pricing tends to win above ~1,000 ops/month.
USE CASE 02Complex branching logic where a single submission needs to fan out to four different apps with conditional logic.
USE CASE 03Real-time pipelines — Make scenarios run on receipt rather than polling, so latency is sub-second.
USE CASE 04Migrating off Zapier when costs balloon — Make often replicates the same workflows at half the price.
USE CASE 05Pre-processing form data before delivery — calling enrichment APIs, transforming JSON, filtering spam — inside the scenario before sending to the destination.

Why splitforms for Make?

Make undercuts Zapier on per-task pricing — both work natively with splitforms webhooks. splitforms is free for 1,000 submissions per month, $5/mo on Pro, or $59 for a 4-year plan (15,000 submissions/month, 48 months of access). No per-integration add-on fees.

Frequently asked questions

Is Make really faster than Zapier?

For webhook triggers, yes. Make's webhook module fires immediately when the URL receives a request; Zapier's webhook trigger polls a queue every 1-15 minutes depending on plan. End-to-end you'll typically see Make finish a scenario in seconds where Zapier takes minutes.

What does Make cost?

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.

Should I use Zapier or Make?

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.

Will the same form work in both Make and Zapier?

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.

What if Make is down?

splitforms retries failed webhook deliveries with exponential backoff up to four times. The submission also lands in the splitforms email + dashboard regardless of webhook outcome, so the lead is never lost.

Can I trigger Make modules from splitforms via Zapier instead?

There's no reason to. Both platforms accept generic webhook triggers — splitforms posts directly to Make. Adding Zapier in between just costs extra tasks.