Should I use a Webflow form or an Embed form?

Use the native form for a simple contact form with existing Webflow styling. Use an Embed form when you need multipart uploads, hidden redirect fields, exact markup control, or predictable exported HTML.

Will this work if I export my Webflow site?

Yes, as long as the exported HTML keeps the Form Plume endpoint in the form action. The form posts from the browser to Form Plume, so it does not depend on Webflow hosting.

Can I use a custom Webflow thank-you page?

Yes. Add a hidden _redirect field with a Webflow page path such as /thanks or an absolute URL. Form Plume redirects successful submissions there.

Can Webflow form submissions trigger Slack or Google Sheets?

Yes. Form Plume can send email, store the submission, and fan out accepted messages to integrations such as Slack, Discord, Google Sheets, Mailchimp, ActiveCampaign, or signed webhooks.

Does Form Plume work with Webflow?

Yes. Form Plume gives you one endpoint that works from your Webflow site. Start with the quickstart docs, then drop the endpoint into your form.

Where do Webflow form submissions go in Form Plume?

Submissions are stored in your Form Plume dashboard, sent to your email, and can trigger integrations like webhooks, Slack, Discord, Google Sheets, Mailchimp, and ActiveCampaign. See the feature overview for the full flow.

Can I try Form Plume before wiring it into my Webflow site?

Yes. You can create an endpoint on the free plan, test it from localhost, preview, or a staging URL, and upgrade only when your form volume or team needs grow. Compare limits on pricing or ask a question on the contact page.

New:Build with AI agents

Webflow contact forms
without brittle backend glue.

Use Webflow's native form action or an Embed form to send submissions to Form Plume. Keep the visual build in Webflow while Form Plume handles email, spam filtering, uploads, dashboards, integrations, and webhooks.

Free foreverNo credit cardWebflow endpoint ready in under a minute

webflow-embed.html

<form
  action="PASTE_YOUR_FORM_PLUME_ENDPOINT_HERE"
  method="POST"
>
  <input type="hidden" name="_redirect" value="/thanks">

  <label for="wf-name">Name</label>
  <input id="wf-name" name="name" required>

  <label for="wf-email">Email</label>
  <input id="wf-email" type="email" name="email" required>

  <label for="wf-message">Project details</label>
  <textarea id="wf-message" name="message" required></textarea>

  <button type="submit">Send message</button>
</form>

The full guide

A hosted backend for your Webflow form.

Connect a live Webflow form to a Form Plume endpoint, choose the right native or embed path, and publish with redirects, uploads, and integrations ready.

1
Create your Form Plume accountStart free and give your Webflow form a hosted endpoint for email, submissions, spam filtering, uploads, integrations, and webhooks.Start free
2
Create the form and copy the endpointCopy the endpoint URL from Form Plume. It looks like https://api.formplume.com/f/your-slug
3
Connect it inside WebflowPaste the endpoint into a Webflow form action or into an Embed form when you need full HTML control. Publish the site and send one test submission from the live domain, not only the Designer preview.

You can use this AI prompt to hand the platform-specific wiring to an assistant without accidentally creating a backend.

You are helping me integrate a Webflow contact form with Form Plume.

Important:
- Do not create a Form Plume account or form for me.
- If I have not provided a Form Plume endpoint yet, stop and ask me for it.
- Tell me to get the endpoint by signing up at https://formplume.com/signup, creating a form, copying the endpoint URL, and pasting it back into this chat.
- Only update code after I provide the endpoint or explicitly confirm the placeholder should stay.

FORM_PLUME_ENDPOINT="PASTE_YOUR_FORM_PLUME_ENDPOINT_HERE"

After the endpoint is available:
- Set the form action or submission target to FORM_PLUME_ENDPOINT.
- Use method="POST" for a plain HTML form.
- Do not add a custom backend, database table, SMTP client, PHP mail handler, serverless function, or email provider.
- Preserve the existing visual styling unless I ask you to improve it.
- Make sure every input, textarea, and select that should be submitted has a name attribute.
- Use clear field names such as name, email, message, company, phone, subject, budget, page, source, and attachment.
- If the form includes files, use enctype="multipart/form-data".
- If I want a custom success page, add a hidden _redirect field with the URL or path I provide.
- Use Webflow's custom form action when the existing native form can keep its fields and styling.
- Use an Embed element with a plain HTML form when the project needs multipart uploads, hidden fields, or markup Webflow's native form UI does not expose.
- Add a hidden _redirect field only if I provide a thank-you URL.
- Remind me to publish and test on the live Webflow domain.

After implementation, tell me exactly which file or editor area changed, where the endpoint is configured, and how to test one real submission.

Choose the Webflow integration path

Webflow gives you two practical ways to connect a contact form to Form Plume.

Use the native Webflow form element when the existing design already works and you only need to change where the submission goes. Set the form action to your Form Plume endpoint, keep method="POST", and make sure each input has a stable name.

Use an Embed element when you need full HTML control: multipart file uploads, hidden metadata, a custom _redirect, or markup Webflow's form settings do not expose cleanly.

Either way, Form Plume becomes the hosted form backend. Webflow serves the page; Form Plume receives the submission, sends email notifications, stores the lead, filters spam, accepts uploads, and triggers integrations or signed webhooks.

Wire the native Webflow form

In the Webflow Designer, select the form element and open form settings. Paste the Form Plume endpoint into the custom action field and set the method to POST.

Review the input settings for each field. The label can be whatever fits the page, but the name should be clear: name, email, message, company, phone, budget, or source.

Publish the site before testing. Webflow previews are useful for layout checks, but the live published page is the environment that will send real submissions and redirects.

If you export a Webflow site, confirm the exported HTML still contains the Form Plume endpoint. The form does not need Webflow hosting to submit, but the static output needs the final action URL.

Use an Embed element for full control

For more advanced forms, drop an Embed element where the Webflow form sits and paste a complete HTML form.

<form
  action="PASTE_YOUR_FORM_PLUME_ENDPOINT_HERE"
  method="POST"
  enctype="multipart/form-data"
>
  <input type="hidden" name="_redirect" value="/thanks">
  <input type="hidden" name="source" value="webflow-contact-page">
 
  <label for="name">Name</label>
  <input id="name" name="name" autocomplete="name" required>
 
  <label for="email">Email</label>
  <input id="email" type="email" name="email" autocomplete="email" required>
 
  <label for="attachment">Brief or file</label>
  <input id="attachment" type="file" name="attachment">
 
  <label for="message">Project details</label>
  <textarea id="message" name="message" rows="5" required></textarea>
 
  <button type="submit">Send request</button>
</form>

Webflow can still style the surrounding section. The embedded form can use your existing utility classes or a small CSS block if the design needs exact spacing.

Add a hidden redirect

Webflow's native success state is fine for simple forms. If you want visitors to land on a real thank-you page, add a hidden _redirect field.

<input type="hidden" name="_redirect" value="/thanks">

Use a Webflow page path for the same site or an absolute URL for a cross-domain handoff. A dedicated thank-you page is easier to track in analytics and gives visitors a clear next step.

Know where native Webflow forms stop

Webflow's built-in form handling is convenient, but it is not the same as a full contact-form backend. You may run into limits around export behavior, file upload behavior, notification routing, or handing accepted leads to other tools.

Form Plume keeps the form simple while adding the backend pieces Webflow is not meant to own: submission history, spam filtering, email notifications, file storage, integrations, and signed webhooks.

Test the published form

After publishing, submit with a real email address you can receive.

Check that the message lands in Form Plume, the email notification is readable, the redirect works, and any Slack, Google Sheets, Mailchimp, ActiveCampaign, or webhook integration receives only the fields you intended to send.

If the submission does not arrive, inspect the live page source and confirm the form action is exactly the Form Plume endpoint.

Primary sources

FAQ

Webflow form questions
before you publish.

Yes. Use Webflow's custom form action when the native form settings fit, or use an Embed element with a plain HTML form. Form Plume receives the POST request and handles email notifications, dashboard storage, spam filtering, uploads, integrations, and webhooks.

One line. Zero backend.

The form backend you don’t have to build.

Free foreverNo credit cardSet up in under a minute

Webflow contact forms without brittle backend glue.