βοΈWebhook Form
Webhook Forms enable form submissions to get sent to an email address and optionally third-party services like Airtable, n8n, or Zapier.
Name change: Webhook Forms used to be called "Forms." However, Forms are now a different component intended for building searches and filters.
Receiving Form Submissions
Webhook Forms are used when you need to send form submission data to an external service, rather than modifying page content like searches and filters.
Email Notifications
By default, submissions are sent to the Project owner.
Pro feature: You can customize the recipient of email notifications by navigating to Project Settings > General.

Webhooks
You can also send form submission data to a webhookβan external URL that receives the data and triggers an action, such as adding a contact to an email automation platform.
Obtain a webhook URL from a third-party platform such as Airtable.
Paste the URL into the
Actionfield in Webhook Form > Settings.
Once set up, every form submission will send a payload (form fields and values) to the webhook URL.
Using the Webhook Form Component
You can add a Webhook Form Component to your canvas from Components Panel > Data section.
Webhook Forms do not submit inside the Builder, including in Preview. They only submit on the published site.
Webhook Form Structure
A Webhook Form consists of three nested instances:
Form Content β The primary form fields.
Success Message β Displayed upon successful submission.
Error Message β Shown when an error occurs.
You can add new Components to further expand and modify your form.
Form States
Webhook Forms automatically switch between states based on submission results.
Success Message
When a submission is successful, users will see a success message. To customize it:
Select the main "Form" instance and go to Settings.
Change the State from "Initial" to "Success."
Edit the success message directly on the canvas.
Error Message
If thereβs an error during submission, users will see an error message. To modify it:
Select the Webhook Form Component.
Set the State to "Error" to preview and edit the error message.
Form Inputs
Each input field must have a name attribute for its data to appear in email notifications and webhook payloads.
Ensure every form input has a value for the name field to be included in submissions.

For a full list of input types, including checkboxes and radio buttons, refer to Form Inputs.
Input Properties
Each input field has several configurable properties in Settings:
Name: The field identifier used in submissions (required for data to appear)
Type: Define the input type (text, email, tel, etc.). Setting type to "email" enforces email format validation.
Placeholder: Hint text shown inside the input before user enters data (e.g., "[email protected]")
Required: When enabled, the form cannot be submitted without this field
Autofocus: When enabled, this field is automatically focused when the page loads
Styling Form States
You can create interactive form styling using states in the Style panel:
Hover: Apply styles when users hover over an input (e.g., wider border, box shadow)
Focus: Apply styles when an input is active/selected (e.g., colored border, glow effect)
Placeholder: Style the placeholder text appearance
To apply state-specific styles, select the input element, open the state dropdown in the Style panel, and choose the state you want to customize.
Bot Protection
Webstudio forms include built-in bot protection to prevent spam submissions. This protection works automatically without requiring any additional configuration β no CAPTCHAs needed. The system analyzes submission patterns to distinguish between legitimate users and automated bots.
Related
Form β Standard HTML forms
Input β Text input fields
Button β Submit buttons
n8n Integration β Automate form workflows
Zapier Integration β Connect to other apps
Last updated
Was this helpful?
