Forms built from the plugin's own schema.
Forms are where a website stops being a brochure. WPPilot Pro covers six form plugins with 162 typed abilities between them. The agent reads the real field-type schema, builds the form, adds notifications and confirmations, and stops before anything touches a live inbox.
Form brief
This is the whole input.
The riskiest part of a form is not the fields. It is where submissions go. Keep routing approval on your side of the line, exactly as this brief does.
Paste into your AI client
PROJECT TYPE: FORM AND LEAD CAPTURE
FORM PLUGIN: [WPFORMS / GRAVITY FORMS / FLUENT FORMS / FORMIDABLE / CONTACT FORM 7 / NINJA FORMS]
PURPOSE: [CONTACT / QUOTE REQUEST / APPLICATION / REGISTRATION / SUPPORT INTAKE] for [AUDIENCE].
FIELDS: [LIST EACH FIELD, ITS TYPE AND WHETHER IT IS REQUIRED]. Inspect the field-type schema first and tell me if any type I asked for is not supported.
LOGIC: Conditional fields, show [FIELD] only when [CONDITION], and only if this plugin genuinely supports it.
VALIDATION: [RULES]. Keep required fields to the minimum that makes the submission useful.
NOTIFICATIONS: Draft the notification to [RECIPIENT] with subject [SUBJECT], but do not enable it until I confirm the address.
CONFIRMATION: [MESSAGE / REDIRECT TO PAGE]. Show me the wording before it goes live.
CONSENT: Include [CONSENT TEXT] and link the privacy policy. Do not collect data the purpose does not need.
PLACEMENT: Embed on [PAGE] in [BUILDER], matched to the existing design system.
DO NOT: Send a test submission, connect a CRM, or enable notifications without my explicit approval.One prompt from you becomes hundreds of typed ability calls from the agent, each one checked against your WordPress capabilities, the active safety profile and the confirmation rules before it runs.
What happens next
The run, step by step
Nothing here is a black box. Every step is a typed call you can see in the change log afterwards.
- 1
Reads the field-type schema first
Every form plugin has its own field vocabulary. The agent asks the installed plugin what field types exist before building, so an unsupported type is reported rather than approximated.
- 2
Creates the form and its fields
Form created, fields added in order with their labels, types, required flags and validation. Fluent Forms, Gravity Forms, WPForms, Formidable and Ninja Forms each have their own typed add-field and edit-field abilities.
- 3
Adds conditional logic where the plugin supports it
Conditional fields are built through the plugin's own logic system. Where a plugin does not support what you asked for, the run says so instead of faking it with duplicate forms.
- 4
Drafts notifications without arming them
Notification and confirmation records are created and left for review. Recipients, CRM routing and success behaviour are the parts a wrong guess makes expensive.
- 5
Embeds the form in the page
Placed into the builder document with your existing classes applied, so the form looks like the site rather than like the plugin's default stylesheet.
- 6
Hands back a test matrix
What to test, validation, spam handling, consent, success state, duplicate submissions, as a list. The agent does not send a live test lead on its own.
Plugins it can drive
It works with what you already run.
WPPilot Pro ships 53 integration families. A module only registers once its plugin is detected on the site and a Pro licence is active.
Builders for placement
Builder-native forms
Downstream
Under the prompt
The abilities this run actually calls
Real registered ability names from the shipped plugin source. Each one has a schema, a permission check and a risk classification.
Where it stops
What stays yours.
Speed is only useful if you can trust the result. These are real constraints in the plugin source, not a disclaimer paragraph.
Read the security model- Notification recipients and CRM routing stay a human decision. The agent drafts them; you arm them.
- It does not send test submissions. A live submission can trigger email, automation and downstream systems that no database rollback can recall.
- Field types that the installed plugin does not support fail closed. No silent substitution of a text input for a missing field type.
- Submission data is personal data. Ask for the minimum the purpose needs, and keep consent text and privacy links in the form.
- Deleting forms, fields, notifications or submissions is destructive and needs explicit confirmation.
Questions
Build forms and lead capture, answered
Which form plugin has the deepest coverage?
Formidable (39 abilities) and Fluent Forms (37) are the widest, followed by WPForms and Gravity Forms at 28 each. Contact Form 7 is the lightest at 9 because the plugin itself has a smaller surface.
Can it connect the form to my CRM?
It can draft the configuration where the plugin exposes it, but arming the connection is your call. An agent that quietly wires a lead form into a live CRM is a support ticket waiting to happen.
Will it test the form for me?
It hands you a test matrix rather than submitting. Live submissions fire notifications and automations that cannot be undone by rolling back a database row.
Can it rebuild a form from one plugin in another?
Pro ships a form-model-migration skill for exactly that. Treat it as a supervised migration: field types do not map one-to-one between plugins, and the differences are where submissions get lost.
Your site · your policy · your AI client
Send the brief. Get the forms and lead capture.
Install WPPilot Free to connect your AI client, then add Pro for the builder, commerce and plugin modules this run depends on.