Forms & Leads

Any form element you add to a page — through AI chat, the visual editor, the code editor, or MCP — is captured automatically the moment your site is built, whether that's a Preview or a real Publish. There's no form-builder step, no action URL or webhook to configure, and nothing to connect to a third-party backend. Every input, textarea, and select just needs a name so its value is identified in the submission — an unnamed field is silently dropped, not an error.

Every submission lands in the Leads tab of your site's workspace, newest first. Filter to one form to see its real field names as columns instead of raw data, rename a form for your own reference, turn on an automatic confirmation reply to whoever submits (available on every plan, though the daily send volume scales with your plan), and export everything to CSV.

Give an input type="file" to let visitors attach something — a resume, a contest photo, a signed document — and it's stored and reviewable right alongside the rest of that submission.

Beyond the default email you get for every submission, a form can route up to 5 additional, conditional notifications from the same Leads tab — for example, alerting your sales team only when a budget field crosses a threshold. Each one has its own recipient, subject, and body (with {all_data} or {field.fieldName} merge tags to include what was submitted), plus optional conditions — a notification with none always sends; with any set, every condition must match. Nothing to build: plain fields, no separate rule-builder. The panel always shows how many of the 5 you've used, and while writing a subject or body you can click any of your form's real field names to insert the right merge tag instead of typing it from memory.

If your site has a WordPress connection configured (see WordPress), a form can optionally relay every submission into that WordPress site's Fluent Forms plugin, in addition to — never instead of — landing in your Leads tab here. Pick the connection and which Fluent Forms form to send to, map your form's fields to that form's real field names, and send a test entry before saving. This is one-directional (your site to WordPress only) and best-effort: a delivery failure is shown right on the affected submission in the Leads tab, but never blocks or loses the submission itself. The point is to reach whatever CRM or automation you already have wired up to that Fluent Forms form, without Zitegen needing its own dedicated integration for it. If discovering forms/fields or sending a test entry fails, the error names the actual cause instead of a bare status code — most often that the connected WordPress user needs to be an Administrator (or granted "Manage Forms" access) to browse forms, even though a lower-permissioned user can already submit fine. Once a test entry does go through, it's sent with values the target field will actually accept — a real-looking address for an email field, one of the field's own options for a dropdown or radio — so validation on the WordPress side doesn't reject it. A form's Layers row in the canvas editor shows which form it is and where it's currently configured to go, e.g. "Contact Form · Zitegen + WordPress" — handy once a site has more than one form.

The list_leads MCP tool gives an agent (Claude Code, Cursor, or any MCP client) the same read access as the dashboard — paginated, filterable to one form, with that form's real field names. The manage_form tool goes further, letting an agent configure a form's submit-outcome messages, upload limits, an outbound webhook, and its custom notifications — see Zitegen MCP tools.