WAITLIST · WEBFLOW

Waitlist for Webflow

Pre-launch capture form with optional referral source. Free for 500 submissions per month — no backend, no SDK, no plugin.

Get free access key Copy the code

500/mo free·no card·drop-in for Webflow

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

500

submissions / mo, free

fields, ready to ship

code outputs

60s

from copy to inbox

§ 00Webflow + Waitlistplatform-specific integration guide

Why Webflow developers choose splitforms for waitlist

Webflow's built-in form block sends to Webflow's own backend, which caps at 100 submissions/month on the free plan and lacks webhook delivery, CC recipients, and spam filtering. The waitlist on this page bypasses that entirely — paste it into a custom embed element, set the form action to splitforms, and you get 500 dashboard submissions/month with AI spam filtering; Starter adds Slack/Discord webhooks. Webflow's native interactions (success message, loading state) still work if you use <code>fetch</code> instead of a native form submit.

§ 00Quick answerHTML · marketing

Yes — this is the shortest safe path for Webflow.

Use the HTML snippet on this page, keep the waitlist fields visible in your Webflow UI, and let splitforms handle delivery, spam filtering, storage, and webhooks.

best implementation

Paste the HTML version, then replace YOUR_ACCESS_KEY.

The posted payload contains email, name, how did you hear about us?. Required fields are email.

native webflow reality

use case fit

Pre-launch waitlists let you capture demand before the product ships. The multi-step form qualifies the use case so launch-day conversions skew toward the highest-intent signups.

§ 01Waitlist × Webflowwhy this combination, in 80 words

Built for Webflow developers who hate operating a backend.

Splitforms is the form backend for Webflow sites. One POST endpoint, no SDK, no plugin — drop the waitlist into a page and ship.

Splitforms is the form backend for Webflow sites. One POST endpoint, spam filtering, and a real dashboard — drop-in, no server, no PHP. Free for 500 dashboard submissions per month; Starter adds email, signed webhooks, exports, and retained uploads; Pro is $5/mo for 5,000.

✦ what you get on the free plan

✓500 form submissions per month
✓2 forms on Free; unlimited forms on Pro
✓Spam protection (honeypot + classifier)
✓Webhooks: Slack, Discord, WhatsApp, custom
✓CSV export of all submissions
✓Email notifications (CC and BCC on Pro)

§ 02Copy-paste codeHTML · 23 lines

Drop into any Webflow project.

Replace YOUR_ACCESS_KEY with your splitforms key, paste into a Webflow page, and ship. No build-time integration required.

form.htmlhtml23 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
03  <input type="hidden" name="subject" value="New waitlist signup">
04 
05  <label for="email">Email *</label>
06  <input id="email" type="email" name="email" placeholder="you@example.com" required>
07  <label for="name">Name</label>
08  <input id="name" type="text" name="name" placeholder="Optional">
09  <label for="referral">How did you hear about us?</label>
10  <select id="referral" name="referral">
11    <option value="">Choose…</option>
12    <option>Twitter</option>
13    <option>Friend</option>
14    <option>Search</option>
15    <option>Newsletter</option>
16    <option>Other</option>
17  </select>
18 
19  <!-- honeypot — bots fill every field -->
20  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" autocomplete="off">
21 
22  <button type="submit">Send</button>
23</form>

§ 03Setup3 steps · 60 seconds · zero config

Generate, embed, receive.

Three actions stand between you and your first waitlist submission. None of them require a backend, a database, or a CAPTCHA library.

STEP 01GENERATE

Generate a free splitforms key

Create your form

key=sk_live_••••••••

STEP 02EMBED

Paste the waitlist into your Webflow project

Drop the form snippet into a Webflow page, component, or layout. Replace YOUR_ACCESS_KEY with the key from your dashboard. The form action is a hard-coded URL — no env vars or build-time wiring needed.

snippethtml

<form action="https://splitforms.com/api/submit" method="POST">
  …
</form>

STEP 03RECEIVE

Receive submissions

Dashboard updates live on Free. Starter adds email delivery, signed webhooks, CSV export, Slack/Discord forwarding, and BCC to your team.

inbox · 1 newjust now

FROM contact@yoursite.com

New waitlist signup

Maya Iyer maya@studio71.co

Loved the demo — quick question about pricing on the 3-year plan. Are usage limits per project or account-wide?

§ 03bWaitlist Signup Form (Pre-Launch Lead Capture)template-specific playbook

The reason this waitlist exists.

Multi-step (Typeform-style) · webhooks into Loops / ConvertKit / Beehiiv.

why it matters

Waitlists are the cheapest growth tool a pre-launch product has — Superhuman, Notion, and Linear all built sizable waitlists before paid launch. The form captures email plus a question or two on use case ('what would you use this for?', 'what tools do you use today?') so the launch sequence segments by intent. Multi-step flow boosts completion vs a single form — the prospect commits in step 1 and answers the qualifying questions in step 2-3 with momentum. Push waitlist signups to a dedicated ESP audience (Loops, ConvertKit, Beehiiv) so launch-day emails segment by use case and target the highest-intent signups first.

route the submission

Step 1: capture email

Single email field — keep step 1 frictionless. Loss-rate from email-only is near-zero; once the email is in, momentum carries through later qualifying questions.

Step 2-3: qualify use case

One or two questions on use case ('what problem brings you here?', 'what tools do you use today?'). Optional but most users complete because they're invested by step 2.

Push to ESP segment

Webhook to Loops / ConvertKit / Beehiiv / Mailchimp into a 'waitlist' audience. Launch-day emails segment by use case so the highest-intent signups get the first invite waves.

§ 03cWebflow production notesnative path · deploy · gotchas

What changes when this waitlist lives in Webflow.

These notes come from the Webflow platform registry and are rendered on this template page so crawlers see the framework-specific answer without opening a separate guide.

without splitforms

Webflow's built-in Forms feature delivers submissions to your Webflow project dashboard and emails them — but the free Site plan caps submissions (50 per site, lifetime, on legacy plans) and webhooks are gated behind the Workspace plan ($24/mo+). Worse, the form fails silently if you exceed the cap: users see the 'success' state, your inbox gets nothing. There's no API to inspect submissions programmatically below the Workspace tier, and CMS-driven forms inherit the same caps. Native is fine for a personal portfolio with three submissions a year; for any real lead capture, you need an external endpoint. Splitforms is that endpoint without the plan upgrade.

deploy notes

Webflow hosts your published site on its own CDN — there's no Vercel/Netlify config to worry about. The form posts cross-origin to splitforms regardless. Disable Webflow's built-in hCaptcha for the form (Form Settings → Spam Filter → Off) — it intercepts submissions client-side before splitforms is reached. Lock the splitforms access key to BOTH your *.webflow.io staging URL and your custom domain in the dashboard; Webflow serves both, with different Origin headers. Custom code embeds count toward Webflow's per-page code limit (10 KB) — keep raw-HTML Embed forms tight if you have multiple per page.

Webflow gotcha

Webflow strips custom hidden inputs from native Form Blocks

If you add <input type="hidden" name="access_key"> directly in Designer's Form Block, Webflow ignores it on publish. Use the Form Block's settings panel: Form Settings → Form Name + add custom attribute. Or use an Embed element with raw HTML if you need full control.

Webflow gotcha

Default action URL gets reset on every Designer save

Setting the Action URL to https://splitforms.com/api/submit in the Form Block sometimes reverts to Webflow's default after a publish. The fix: lock it in by adding a custom attribute action to the form element (Settings → Element Settings → Custom Attribute).

Webflow gotcha

Method must be set to POST in the form's settings, not the URL

Webflow forms default to GET. Open the form's Settings panel, change Method to POST. If you forget, the submission posts your fields as URL query params — splitforms returns a 405 Method Not Allowed.

Webflow gotcha

Webflow's success/error elements still trigger on AJAX submit

Webflow auto-shows the .w-form-done div on a 2xx response. That's good — but if you also set up a redirect field in splitforms, the user sees the success message for ~80ms before the redirect fires. Either remove the success div or skip the redirect field.

PATTERN A

Pattern A — native Form Block with overridden action URL

Use Webflow's drag-and-drop Form Block — keep the styling, structure, and Designer integration. In Form Settings, change Action to https://splitforms.com/api/submit and Method to POST. Add a hidden access_key field via the form's settings panel. Submissions skip Webflow's backend entirely. Use the same wiring for the waitlist fields on this page.

pattern-a.htmlhtml8 lines

01<!-- After saving in Designer, the published HTML looks like: -->
02<form action="https://splitforms.com/api/submit" method="POST">
03  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
04  <input type="text"  name="name" required />
05  <input type="email" name="email" required />
06  <textarea name="message" required></textarea>
07  <input type="submit" value="Send" />
08</form>

PATTERN B

Pattern B — Embed element with raw HTML

If you need full control over markup (custom honeypot, file upload, multi-step), drop an Embed element on the canvas with raw HTML. Skips Webflow's form widget entirely. Useful for forms that don't fit the Designer's mental model. Use the same wiring for the waitlist fields on this page.

pattern-b.htmlhtml8 lines

01<form action="https://splitforms.com/api/submit" method="POST">
02  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
03  <input type="hidden" name="redirect" value="/thanks" />
04  <input name="email" type="email" required />
05  <textarea name="message" required></textarea>
06  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
07  <button type="submit">Send</button>
08</form>

§ 04Field-by-field rundown3 fields · names you POST

What every field actually does.

Each field below ships in the waitlist template — rename, remove, or add your own. Splitforms accepts any name you POST.

emailREQUIRED

Email

Reply-to address — splitforms wires this so hitting reply goes back to the sender.

placeholder · you@example.com

name

TEXT

Name

Greeting + dashboard label so submissions don't all read 'anonymous'.

placeholder · Optional

referral

SELECT

How did you hear about us?

Dropdown — keeps responses normalised so you can filter the dashboard.

TwitterFriendSearchNewsletterOther

§ 05Waitlist on other frameworks21 frameworks · same backend

One backend. Every framework.

The same waitlist template works on every framework splitforms supports. Pick yours.

§ 06Questions9 answered

Waitlist on Webflow — FAQ.

Direct answers, no marketing fluff. Missing one? Email hello@splitforms.com.

01Does this waitlist work on Webflow?

Yes. The form is plain HTML with a single POST endpoint, so it runs on any Webflow site without server-side code, plugins, or SDKs. Drop the snippet into a Webflow page or component and submissions land in your splitforms dashboard.

02How much does the waitlist cost on Webflow?

Free for 500 submissions per month — no credit card, no trial. Pro is $5/mo for 5,000 submissions, and there's a one-time $59 3-year plan (15,000 submissions/mo for 36 months). The same pricing applies regardless of which framework hosts the form.

03Can I customize the fields?

Yes. The template ships with sensible defaults (email, name, how did you hear about us?…) — add, remove, or rename any of them. Splitforms accepts whatever fields you POST.

04How does spam protection work on the waitlist?

A hidden honeypot field catches dumb bots, and a tuned classifier scores the rest. You only see real submissions in your dashboard. No CAPTCHA, no friction for human users — and it works the same on Webflow as on any other framework.

05Can I send the waitlist submissions to Slack or Discord?

Yes. Webhooks are available on Starter and above, with auto-formatted payloads for Slack, Discord, and WhatsApp (via CallMeBot). Or send raw signed JSON to any URL — Zapier, n8n, your own server. Configure in the splitforms dashboard.

06Will it work on a static Webflow site?

Yes — the form posts directly to splitforms from the browser, so no server is involved. Works on Vercel, Netlify, GitHub Pages, Cloudflare Pages, S3, or any plain Apache host.

07Should I show waitlist position / numbers?

Showing 'you're #347 in line' on the confirmation creates social proof but invites comparison. Showing total waitlist size ('join 2,500 people on the waitlist') without per-person position is the safer middle. Refer-a-friend mechanics that move people up the list (Robinhood-style) drive viral growth but require more eng work.

08How do I trigger launch invites in waves?

Tag waitlist signups by use case in the ESP audience (Loops, ConvertKit). Launch-day, segment by tag and send invite waves over 48-72 hours. Highest-intent / closest-fit goes first; broadest casts go last. Spreads server load and lets you triage onboarding support.

09Can I integrate with Loops / ConvertKit / Beehiiv?

Yes — webhook the JSON. Loops has direct webhook support and is purpose-built for product transactional + waitlist email. ConvertKit and Beehiiv accept via API or Zapier. All three handle the launch-sequence segmentation cleanly.

§ 07Comparisonvs Web3Forms · vs Formspree

splitforms vs everything else.

Same drop-in API. More free submissions, Starter signed webhooks, MCP support no other backend has.

Feature	Web3Forms	Formspree	splitforms
Free monthly submissions	250	50	500
Custom fields beyond contact	Yes	Pro tier	Free
Webhooks (Slack / Discord)	Pro tier	Pro tier	Free, signed
AI / MCP submission inbox	No	No	Yes
Long-term plan (3-year flat)	—	—	$59 every 3 years

§ 08More templates for Webflow5 adjacent patterns

Ship a waitlist on Webflow in 60 seconds.

500 submissions per month, free forever. No credit card. Copy the snippet above and paste it into your Webflow project.

Get free access key →Read the docs

founders pricing locked in · early access open

Waitlist for Webflow

Why Webflow developers choose splitforms for waitlist

Yes — this is the shortest safe path for Webflow.

Paste the HTML version, then replace YOUR_ACCESS_KEY.

Built for Webflow developers who hate operating a backend.

Drop into any Webflow project.

Generate, embed, receive.

Generate a free splitforms key

Paste the waitlist into your Webflow project

Receive submissions

The reason this waitlist exists.

Step 1: capture email

Step 2-3: qualify use case

Push to ESP segment

What changes when this waitlist lives in Webflow.

Webflow strips custom hidden inputs from native Form Blocks

Default action URL gets reset on every Designer save

Method must be set to POST in the form's settings, not the URL

Webflow's success/error elements still trigger on AJAX submit

Pattern A — native Form Block with overridden action URL

Pattern B — Embed element with raw HTML

What every field actually does.

Email

Name

How did you hear about us?

One backend. Every framework.

Waitlist on Webflow — FAQ.

splitforms vs everything else.

Other ready-to-ship Webflow forms.

Ship a waitlist on Webflow in 60 seconds.