FormBucket

Webflow handles form rendering well, but its native submission handling is intentionally basic: email notification, a dashboard, and that's mostly it. If you need to route submissions to a CRM, trigger a webhook, filter spam with custom rules, or pull submission data into a custom dashboard, you need a form backend. FormBucket is one option for adding that layer without writing or running a server.

This page covers three ways to set it up: a direct form action swap that takes a few minutes, a full Code Embed for more control over markup, and API plus webhook integration for teams who need to route submission data across external systems or sync it into the Webflow CMS.

What is FormBucket: FormBucket is a cloud-based form processing service for static sites. It captures form submissions via a unique bucket URL endpoint and stores them in a searchable dashboard. Features include spam filtering, email notifications, webhook automation, and CSV/JSON data export. Both a REST API (v1) and a GraphQL API (v2) are available for programmatic access to submission data.

How to integrate FormBucket with Webflow

FormBucket integrates with Webflow through three approaches: pointing a form's action attribute to a FormBucket bucket URL for fast setup with no code changes to markup, using a Code Embed element to embed a fully custom HTML form that posts directly to FormBucket, and connecting via webhooks and the REST or GraphQL API for submission routing, CMS sync, and custom data workflows. These methods are independent — most sites start with the first and add API-based automation later.

There is no FormBucket app in the Webflow Apps Marketplace. This is a manual integration in all cases.

Point a Webflow form's action to FormBucket

The simplest setup: create a bucket in FormBucket, then add its endpoint URL to your existing Webflow form's action field. No custom markup or Code Embed needed.

To set this up:

1. Create an account at FormBucket and create a new bucket. Each bucket generates a unique URL in the format https://api.formbucket.com/f/YOUR_BUCKET_ID.  
2. In Webflow, select your form element and open its settings panel.  
3. In the Action field, paste the FormBucket bucket URL and set Method to POST.  
4. Publish your site. Submissions will now route to FormBucket instead of Webflow's native handler.

Webflow's client-side validation continues to work normally. Changing the action attribute does not affect HTML5 field validation or any custom JavaScript validation on the page. Spam filtering, email notifications, and the submission dashboard are all configured inside FormBucket.

One practical note: when a form submits to an external endpoint, Webflow's built-in success and error states on the form element no longer fire. To handle post-submission behavior (redirect URL, custom confirmation message), configure the redirect in your FormBucket bucket settings.

Embed a custom HTML form with Code Embed

If you need to control the full form markup for file uploads, honeypot fields, or hidden inputs, embed a custom HTML form using a Code Embed element instead of modifying Webflow's native form.

A basic Code Embed form posting to FormBucket looks like this:

<form action="https://api.formbucket.com/f/YOUR_BUCKET_ID" method="POST">
 <input type="text" name="name" placeholder="Name" required>
 <input type="email" name="email" placeholder="Email" required>
 <textarea name="message" placeholder="Message"></textarea>
 <!-- Honeypot field — hidden from humans, filled by bots -->
 <input type="text" name="_bucket_trap" style="display:none">
 <button type="submit">Send</button>
</form>



For file uploads, add enctype="multipart/form-data" and a file input:

<form action="https://api.formbucket.com/f/YOUR_BUCKET_ID" method="POST" enctype="multipart/form-data">
 <input type="file" name="attachment">
 <button type="submit">Upload</button>
</form>



The honeypot field (_bucket_trap) is a hidden input that human visitors never fill in but bots often do. FormBucket filters submissions where this field contains a value, working in combination with its server-side spam filtering. Confirm exact spam filtering options in FormBucket's documentation, as specific configuration options are not fully detailed in the public OpenAPI spec.

Style the embedded form using Webflow's custom code or by adding a CSS block inside the Code Embed element.

Connect via webhooks and the FormBucket API

FormBucket exposes a REST API (v1) and a GraphQL API (v2) for accessing submission data programmatically. Combined with webhooks, this is the path for routing submissions to external services or syncing data into the Webflow CMS.

Webhooks fire a POST request to a URL you configure whenever a form is submitted. Use webhooks to push submission data to a CRM, trigger an email automation sequence, or kick off a serverless function. Configure webhook destinations inside your FormBucket bucket settings.

The REST API (v1) covers programmatic bucket management and submission retrieval. Authenticate with an API token from your FormBucket dashboard and use the submissions endpoints to fetch, filter, and paginate through stored form data.

The GraphQL API (v2) supports querying submission data with field selection, filtering, and aggregation in a single request, which is useful for building admin dashboards or editorial tools that display form analytics.

The most common developer workflow combining these pieces:

1. A visitor submits a Webflow form pointing to a FormBucket bucket URL.  
2. FormBucket fires a webhook POST to a serverless function (Vercel, Netlify Functions, or Cloudflare Workers).  
3. The function transforms the payload and calls the Webflow API to create a new Collection List item. For example, adding a submitted job application to a CMS collection.  
4. The function also calls a CRM or email API to trigger follow-up automation.

This pattern requires developer resources. It is not a no-code setup, and it requires maintaining a serverless function layer between FormBucket and any downstream systems.

What you can build with the FormBucket Webflow integration

FormBucket handles the submission processing layer that Webflow's native forms leave to you, spam filtering, storage, notifications, and data routing, which opens up a range of form-backed applications that standard Webflow forms cannot support alone. The right scope depends on whether you stay with the direct action swap or build out the webhook and API layer.

Here are a few things you can build:

• Lead capture with CRM sync: Build contact forms on Webflow landing pages that route submissions through FormBucket webhooks to a serverless function, which then creates or updates records in a CRM without third-party automation platforms for straightforward one-way data pushes.  
• File submission workflows: Accept portfolio submissions, support ticket attachments, or application documents via Webflow forms with file inputs, using FormBucket's multipart upload support to store and forward files. It’s suitable for agencies collecting client briefs or HR teams handling applications.  
• Event registration systems: Capture registrations on Webflow pages and route submissions via webhook to trigger confirmation emails and sync attendee data into a Webflow CMS collection, keeping a published attendee list in sync with incoming form data.  
• Customer feedback portals: Embed multiple FormBucket-backed forms across a Webflow site like product feedback, NPS, support requests, then pull consolidated submission data through the FormBucket API into a custom dashboard or reporting tool.

To get started, create a bucket at FormBucket and point your first Webflow form's action attribute to the bucket URL. For API and webhook integration, the Webflow API documentation covers CMS item creation endpoints.