Forms Overview
How UiChemy turns any HTML form inside a UiChemy Composer widget into a managed form: submission storage, email notifications, webhook delivery, and built-in spam protection.
UiChemy's form system works on a simple idea: any HTML <form> element inside a Composer widget can become a fully managed form once it's marked as one. No separate form plugin, no drag-and-drop form builder, no shortcodes. Mark it as a form, in code or from the Layers panel, and UiChemy handles the rest. See Turn Any Element Into a Form for both methods.
Why It Matters
Form logic stays in the same place as the rest of your Composer widget, not a separate plugin with its own settings screen. There's nothing extra to install, update, or keep in sync with your builder.
How It Works
Once a form is marked, in code or from the Layers panel, UiChemy intercepts its submission and routes it through its own secure processing endpoint. From there, it can:
- Store the submission in your WordPress database, visible in UiChemy → Form Submissions.
- Send an email notification to one or more addresses with the submitted data.
- Fire a webhook to a URL you specify, for CRM integrations, Zapier, Make, or any service that accepts POST data.
These actions can be used independently or in any combination:
- Save to database and Email a notification, each with its own switch. Both are on for a new form.
- Send to a webhook, its own switch, then a Webhook URL.
- CC, an extra email recipient, under Email a notification → More options.
Configuration happens in the Composer widget's own "On submit" panel, not in the HTML, which means sensitive details like email addresses and webhook URLs are never exposed in the page source.
Security Built In
Every UiChemy form gets three spam protections automatically, you don't need to configure them:
- Security token. Every form carries a token that the server checks before processing a submission, which stops submissions sent from outside your site. It works the same for logged-in and logged-out visitors, and on cached pages.
- Honeypot. A hidden field is added to every form that no real user can see or fill in. Bots that fill in all fields trigger the honeypot and are rejected silently. No CAPTCHA needed for basic spam protection.
- Rate limit. Each visitor can submit up to 5 times a minute. After that they see "Too many submissions. Please wait a moment and try again."
What Gets Stored
| Field | What it stores |
|---|---|
| Form Name | The form name you gave it, for example Contact |
| Page | The URL of the page the form was submitted from |
The email address from the submission (if a field is named email) | |
| All Fields | Every named input field and its value |
| Status | Read or Unread |
| Submitted At | Date and time of submission |
The Form Submissions Dashboard
Go to UiChemy → Form Submissions to view everything submitted across all your forms. You can filter by form name, filter by read/unread status, open any submission to see the full field data, and export to CSV (UiChemy Pro).
Whether a form saves its entries is set per form, with its Save to database switch. With it off, submissions are still processed (emails sent, webhooks fired) but nothing is saved to the database.
Supported Form Scenarios
| Scenario | Supported |
|---|---|
| Contact forms | Yes |
| Lead capture / newsletter signup | Yes |
| Multi-field data collection | Yes |
| File upload fields | Planned |
| Multi-step forms | Possible with JavaScript |
| WooCommerce checkout | No, use WooCommerce's own checkout |
Use Cases
- Adding a contact or lead-capture form to any page you build in Composer, without installing a separate form plugin.
- Sending captured leads straight to a CRM or automation tool with Send to a webhook.
- Building a form inside a Theme Builder template (header, footer) that works the same as one on a regular page.