Build WordPress forms with AI from each plugin's own schema.

Decide what the form is for before you build WordPress forms with AI

An agent will happily build a twenty-field form if the brief lists twenty fields. The useful work happens before that: decide what a good lead looks like and ask only for what you need to qualify and answer it. A quote form for a tradesperson needs the job type, the postcode and a way to reply. A support intake needs the account or order reference so the reply does not start with a question. Everything else is friction and personal data you now have to look after.

Write the brief from the reply backwards. List what the person answering needs in front of them, mark each field required or optional, and say which answers should change what comes next. That last list becomes the conditional logic, and it is where plugins differ most, so the agent checks the installed plugin's field-type schema before it promises anything.

Walking through a Gravity Forms quote request

Here is the order a careful run follows for a quote form in Gravity Forms embedded on an Elementor page. The other supported plugins follow the same shape with their own ability names.

• gravityforms-check-setup reports the plugin version and what it can do; gravityforms-get-field-types-schema lists the field types this install actually has.
• gravityforms-create-form makes the empty form, and gravityforms-add-field adds each field in order with its label, type, required flag and any conditional rule; gravityforms-reorder-fields fixes the order if the review changes it.
• gravityforms-create-confirmation writes the on-screen message or redirect you approved word for word.
• Notifications stay a proposal. gravityforms-create-notification exists, but the recipient address is yours to confirm, and the brief keeps it unsaved until you have.
• The form is placed on the page through the builder's own form or shortcode element, then audit-accessibility checks the served page for missing labels on its fields.

Free reads entries, Pro builds forms

The edition line here is clear. GoBuildWP Free can list forms and their entries on several plugins: cf7-list-forms and cf7-list-entries, gravityforms-list-forms and gravityforms-list-entries, wpforms-list-forms and wpforms-list-entries. That suits an agent that summarises what came in this week. Note that WPForms stores entries only in WPForms Pro; on WPForms Lite there are none to read.

Creating forms, adding and editing fields, confirmations and notifications is Pro, as are the entry tools that change something, such as gravityforms-mark-entry for read and starred flags, and the exporters. The Gravity Forms export redacts password, card, file-upload, signature and IP columns unless you explicitly confirm you need them, which is the right default for a lead list leaving the site.

Test the form from submission to the receiving inbox

A saved form is only the start of the check. On a phone, use the form with the keyboard and confirm that required fields, validation messages and conditional branches make sense. Try an incomplete submission as well as a valid one. Have the recipient approve the destination address and subject line before enabling notifications; a confirmation message on the page does not prove that email arrived.

Then submit the form yourself, once, on staging, after notifications are armed. Check the email arrives, the entry is stored, the confirmation reads correctly, and any downstream automation fires once rather than twice. Repeat on production at launch with a clearly labelled test entry. The agent deliberately does not do this step: a submission can reach inboxes and CRMs that no rollback can recall.

Changing a form that is already collecting leads

Live forms deserve the same caution as live pages. Rather than editing in place, duplicate it first: wpforms-duplicate-form copies fields, settings, notifications and confirmations into a new form that starts as a draft unless the call asks for publish, so the agent can change the copy while the original keeps taking enquiries. The copied notifications keep their recipients, so review them before the copy goes anywhere a visitor can submit it. Swap the embed once you have tested the copy.

Watch for whole-field replacement. wpforms-edit-form replaces the entire field map when fields are passed, so the agent should read the form first and use the individual add, edit and delete field abilities for small changes. Field and form deletions are destructive and need a confirmation flag on the call. WPForms field and form changes keep a before-image of the form, but a forced form delete is permanent and entries live in WPForms' own tables, out of the ledger's reach, so export the entries before any structural change so the record of past leads does not depend on the form staying as it was.