splitforms.com

Integration · Make

Send form submissions to Make.

Send form submissions to Make to trigger scenarios.

  • 500 free / mo
  • No credit card
  • Live in minutes
splitforms sends every form submission to Make

Form submissions, routed automatically

splitforms connects your forms to Make and moves every submission across the moment it's received — no manual export, no copy-paste.

Your leads are never lost

Every submission is emailed to you and saved to a searchable dashboard, so the lead is captured even if Make is unreachable.

No per-integration fees

Connecting Make to your forms is included in your plan — no add-on charge and no per-message billing from splitforms.

Example: form markup

Send form submissions to Make from plain HTML.

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.

Get your access key
contact-form.html
<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>

How it works

How to send form submissions to Make.

Here's how to send form submissions to Make in 6 steps — no code required, and most teams finish in a couple of minutes.

Step 1

In Make.com, create a new scenario. Add a Webhook → Custom webhook module as the first step. Make generates a unique URL.

Step 2

Copy that URL and paste it into the form's Webhooks tab in splitforms.

Step 3

Submit a test entry. The Make webhook module will receive a sample payload — Make uses it to derive the data structure for downstream modules.

Step 4

Add scenario modules — Google Sheets, Notion, HubSpot, Slack, anything in Make's library — and map splitforms fields into each.

Step 5

Turn the scenario on. Each splitforms submission triggers a scenario run immediately.

Step 6

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

How do teams send form submissions to Make?

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. Prefer a plainer destination? The same form can also send form submissions to email or forward them to any webhook.

  • Native delivery (auto-detected webhook)
  • Routing high-volume form submissions cheaper than Zapier — Make's per-task pricing tends to win above ~1,000 ops/month.
  • Complex branching logic where a single submission needs to fan out to four different apps with conditional logic.
splitforms routing form submissions to Make

Why splitforms

Do you need a separate tool to send form submissions to Make? No.

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

  • Real-time pipelines — Make scenarios run on receipt rather than polling, so latency is sub-second.
  • Migrating off Zapier when costs balloon — Make often replicates the same workflows at half the price.
  • Pre-processing form data before delivery — calling enrichment APIs, transforming JSON, filtering spam — inside the scenario before sending to the destination.
Every Make submission is saved in the splitforms dashboard

How SplitForms works

From form to workflow in 3 simple steps.

Connect your form, collect every submission, and send data where it needs to go — without building backend infrastructure.

A SplitForms contact form submission launching straight to your inbox

Add your endpoint

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

HTML form pointing at a SplitForms submit endpoint

Receive submissions

We instantly capture and organize every submission in your inbox.

Submissions inbox with searchable leads and status pills

Route anywhere

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

Generic integration tiles for email, sheets, chat, CRM, automate, and webhook

No credit card required. Set up in under 60 seconds.

Connect & automate

Connect your favorite tools and automate everything

SplitForms works with the destinations you route to and the platforms you build on — from Slack and Sheets to WordPress, Shopify, and Next.js.

Connect your SplitForms form to Slack, Google Sheets, Mailchimp, Zapier and more

Trusted by indie teams and agencies shipping forms worldwide

PETAL/COKRAFT.DELINEAR-XBUILD.DEVSTUDIO 71MERIDIANFRAME&CO

Testimonials

Loved by developers shipping at every scale.

40 quotes on record — from indie hacks to agency migrations.

Common questions

Make form integration questions.

View all FAQs
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?

The submission lands in the splitforms email + dashboard regardless of webhook outcome, so the lead is never lost. The failed delivery is recorded as the webhook's last status in the dashboard (deliveries aren't auto-retried today), so you can spot and fix a broken scenario quickly.

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.

Simple pricing

Start free. Scale when you need more.

Choose a plan that fits your workflow — from a free form endpoint to full automations, exports, and higher submission limits.

Free

$0

Free forever

 
Best for testing

For side projects and indie devs.

  • 500 submissions / mo
  • Unlimited forms
  • Email notifications included
  • Honeypot spam filtering
  • Submissions dashboard
  • MCP setup stays free
  • No credit card required

3-Year

$59/ 36 months
was $99 · save 40% · new-user price

Pay $59. 3 years sorted.

  • 15,000 submissions / mo
  • Unlimited forms
  • Everything in Pro
  • Renews every 3 years
  • Long-term discount
  • Priority support included
  • Vote on the roadmap

No credit card required on Free • Cancel anytime