Formserve
Features Templates Pricing Docs Blog FAQ
Sign in Create endpoint
← All guides

Webflow guide

Webflow form backend powered by Formserve

Use an embed or custom form action to send Webflow leads to Formserve.

No backend API route Honeypot spam trap Works with any host

Overview

What you are building

This guide connects an existing Webflow form to Formserve. Keep your current design and let Formserve handle storage, spam checks, notifications, and integrations after submit.

Requirements

Before you start

Endpoint URL

Create a Formserve endpoint and copy the public form URL.

Named fields

Every input, select, and textarea needs a useful name attribute.

Honeypot field

Add _honeypot to reduce spam without showing a CAPTCHA.

Allowed domain

Add the deployed site domain before launch.

Setup steps

Connect the form

1

Create a Formserve endpoint.

Keep the change focused on wiring the existing form to Formserve while preserving the current UI and frontend structure.

2

Add your Webflow domain to allowed domains.

Keep the change focused on wiring the existing form to Formserve while preserving the current UI and frontend structure.

3

Paste an HTML form or update the action URL.

Keep the change focused on wiring the existing form to Formserve while preserving the current UI and frontend structure.

4

Test from the published Webflow site.

Keep the change focused on wiring the existing form to Formserve while preserving the current UI and frontend structure.

Code

Minimal HTML contract

Every framework eventually sends these same fields. If your tool generates a component, ask it to preserve styling and only adjust the submission behavior. 

<form action="https://formserve.io/f/YOUR_ENDPOINT_KEY" method="POST">
  <input type="text" name="_honeypot" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" />
  <input type="email" name="email" required>
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

Testing checklist

  • ✓ Submit a test entry.
  • ✓ Confirm it appears in the Formserve inbox.
  • ✓ Deploy and test from the production domain.
  • ✓ Enable the integrations your workflow needs.

Common mistakes

  • ! Missing name attributes.
  • ! Skipping allowed-domain setup.
  • ! Creating an unnecessary backend route.
  • ! Not showing success or error feedback.