Form Module
Purpose and when to use
The Form module is the main Divi Form Builder module in the Divi 5 Visual Builder. Use it to build complete form workflows, including:
- Contact forms with email notifications
- Frontend create/edit post forms
- User registration and login forms
- Custom, developer-managed submission flows
- Advanced flows with multistep, spam protection, payments, and AI options
Each Form module contains one or more Form Field child modules.
Before you configure this module
Confirm these prerequisites:
- Divi Form Builder is active
- You are editing in the Divi 5 Visual Builder
- You set a unique Form ID
- You selected the right Form Type for your intended workflow
Quick setup workflow
- Add the Form module to your layout.
- Set Form Title, Form ID, and Form Type.
- Add fields with Add New Form Field.
- Configure form behavior in the Content tab.
- Style the module in the Design tab.
- Run frontend tests for success and failure scenarios.
Match form type to outcome
Use this quick mapping before you configure advanced options:
- Contact: send notifications and collect inquiries
- Create Post/Page/CPT: publish or draft frontend submissions
- User registration: create/update user accounts
- Login: authenticate existing users from the frontend
- Custom: run developer-defined processing through hooks
Content tab
The Content tab controls form behavior and submission outcomes.
Main setting groups
| Group | What it configures |
|---|---|
| Main options | Form title, Form ID, Form Type, and form-type-specific behavior |
| Form fields list | Add, remove, and reorder Form Field child modules |
| Layout / submit | Submit button text, AJAX submit, reset/hide behavior, preload options |
| Admin/sender notifications, subjects, sender options, confirmation emails | |
| Notices and redirects | Success/failed messages, redirect rules, and message placement |
| Spam | reCAPTCHA/basic captcha/honeypot validation controls |
| Multistep | Step transitions, progress bar behavior, next/prev flow |
| Price / payment | Payment enablement and payment UI behavior |
| Extra / integrations | Optional integrations such as Bloom or Zapier webhook |
| AI | Form AI controls and limits |
Core settings reference
| Setting | Type | Default | Notes |
|---|---|---|---|
| Form Title | text | (empty) | Title shown above the form |
| Form ID | text | (empty) | Unique identifier for targeting and integrations |
| Form Type | select | contact | Chooses the submission workflow |
| Submit Button Text | text | Submit | Label shown on the submit button |
| AJAX Submit | toggle | off | Submits without full page reload |
| Save To Database | toggle | off | Stores submissions for entries/reporting workflows; required for most reporting pages |
| Success Message | text | Thank you for your message, we will be in touch shortly. | Message shown after successful submit |
| Failed Message | text | Sorry the form was not submitted, %%message%% | Message shown on failure |
| Redirect After Success | toggle | off | Redirects user after successful submit |
| Redirect URL After Submission | text | (empty) | Success redirect target |
| Redirect After Failed | toggle | off | Redirects user after failed submit |
| Redirect URL After Failed | text | (empty) | Failed redirect target |
| Enable Submission Notification | toggle | on | Sends admin notification email |
| Captcha Type | select | none | Spam-protection type |
| Multistep Enabled | toggle | off | Enables step-based progression |
| Form AI Enabled | toggle | off | Enables Form AI capabilities |
Save To Database and reporting dependency
Use Save To Database when you need submission history and reporting beyond one-time email delivery.
When this setting is enabled, successful submissions are stored as entries and become available in:
If Save To Database is disabled, forms can still submit and send emails, but entries/reporting views may show little or no data.
Quick validation flow:
- Enable Save To Database in the Form module.
- Submit one test entry from the front end.
- Confirm the record appears in Form Entries.
- Confirm summary totals update in Reporting.
Design tab
Use the Design tab to control visual output across typography, spacing, colors, buttons, and form-related UI states.
Common areas:
- Label and placeholder styling
- Input/field spacing and alignment
- Success and error message styling
- Submit/next/previous button appearance
- Conditional groups for payment, captcha, and multistep elements when enabled
Advanced tab
The Advanced tab uses standard Divi options:
- Attributes
- Custom CSS
- Conditions and visibility
- Transition, position, and scroll effects
Verify the module is configured correctly
- Submit a test entry from the frontend with valid values.
- Submit another entry with intentionally invalid values.
- Confirm:
- Validation and notices appear as expected
- Redirect behavior is correct
- Email notifications (if enabled) are delivered
- Type-specific behavior works (create post, login, register, etc.)
Common setup mistakes
- Reusing a Form ID already used on another active form
- Using a mismatched Form Type for the intended outcome
- Enabling advanced features (payments, multistep, AI) without frontend validation
- Assuming builder preview is enough without real submission testing
What's Next
- Form Field module reference - Configure type-specific field behavior and validation.
- Form types - Confirm the right workflow for contact, post, user, or login forms.
- Field types - Pick and configure the right controls for each input.
- Reporting - Review saved entries, trends, and payment activity.
- Global settings - Configure plugin-wide AI, spam, and payment defaults.