Escape Webflow's form submission limits with a custom action

Published 2026-07-15

Webflow's native forms are genuinely nice to build with — drag a Form block onto the canvas, style it visually, done. The catch shows up later: on the free Starter site plan, Webflow caps you at a maximum of 50 total form submissions, full stop. Paid site plans raise the ceiling, but there's always a ceiling, and it's sized to your hosting tier rather than how many people actually fill out your form. Hit it, and new submissions stop being collected until you upgrade.

The other catch is ownership. By default, submissions live in Site settings > Forms inside Webflow — there's no export you control, no dashboard search across projects, and no easy way to route a copy anywhere else without paying for the App or Webhook integrations.

You don't need to give up Webflow's form builder to fix either problem. Webflow forms support a Custom action, built for exactly this: sending submissions to an external endpoint instead of Webflow's own handler. Here's the honest, exact click path — no Embed block, no custom code required.

The setup: Custom action, not Embed

You could replace the whole form with an HTML Embed block, but you don't have to — Webflow ships a native way to redirect a form's destination. It's in the same Settings panel you already use to name your form and write success/error messages.

1. Select your Form on the canvas or in the Navigator.

2. Open the Settings panel on the right.

3. Under Send to, remove Webflow and Email notifications if either is checked — Webflow doesn't let you combine those with a custom action; you have to pick one path.

4. Click the add icon next to Send to and choose Custom action.

5. Enter the URL:

   https://api.submissionbuddy.io/f/your-form
   

6. Set the method to POST.

7. Click Save, then Publish.

That's it — no code, no embed. Your form still looks and behaves exactly as you designed it in the Designer; only where the data goes has changed.

One thing to know: it's a real page submit, not AJAX

Webflow's custom action does a standard HTML form POST — a full browser navigation, not a background fetch. If your endpoint just returns a JSON body (SubmissionBuddy's default success response is {"ok": true, "submission_id": "..."}), the visitor's browser will navigate to that raw JSON instead of seeing a friendly confirmation. Webflow users have hit this exact issue when wiring forms to custom endpoints.

The fix is the hidden _redirect field below — it tells SubmissionBuddy to send a 303 redirect to a thank-you page instead of returning JSON, so the visitor lands somewhere designed rather than staring at {"ok":true,...}.

Add spam protection and a thank-you redirect

Webflow field elements are just inputs with a Name setting. Add two more to your form and give them these exact names — no visual difference needed, you're just setting properties in the Settings panel per element:

• A text input named _honeypot. Set its element display to none in the Designer (or drop it in a Div with display: none) so real visitors never see it. Bots that fill in every field will trip it.
• A hidden-style input named _redirect with a Value of your thank-you page, e.g. https://yoursite.webflow.io/thanks.

Both are stripped from the stored submission automatically — they never show up as form fields in your SubmissionBuddy dashboard.

What happens after the visitor clicks submit

The submission is written to durable storage before SubmissionBuddy returns anything to the browser — nothing is held in memory waiting to be processed later. From there it flows through two more stages: a database write (so it's searchable in the dashboard) and an email notification to your team, each retried automatically if a downstream step hiccups.

Because there's no schema, Webflow field names can be anything — rename an input, add a new one, delete one — and nothing needs reconfiguring on the SubmissionBuddy side. Per-IP and per-form rate limiting plus the honeypot field above are on by default on every plan; paid plans can layer on an invisible, privacy-friendly CAPTCHA for more determined bots.

What you get that Webflow's native handler doesn't

• No submission ceiling tied to your hosting plan. The free SubmissionBuddy plan handles 100 submissions/month across up to 2 forms, no credit card required — separate from whatever Webflow site plan you're on.
• A dashboard you can search, filter, and export from. Full-text search across submission values, date-range filtering, sortable columns, and an Excel export — none of which the Webflow Forms panel gives you natively.
• Data that isn't locked to one destination. If you ever move off Webflow, or add a second front end, the endpoint doesn't change.

Worth knowing before you switch

Custom action is all-or-nothing per form — you can't send to both Webflow's own storage and a custom action at the same time (Apps/CRM integrations are separate and can run alongside a custom action if you need that combination). And Webflow's built-in reCAPTCHA element only applies to forms using Webflow's own handler, so once you're on a custom action, spam filtering is on the receiving end — which is exactly what the honeypot field above, plus SubmissionBuddy's rate limiting, are for.

Webflow documentation and community threads checked 2026-07-15. Code and click paths verified against the live SubmissionBuddy API the same day.