Build with AI (Pro)
Describe the form you want, in your own words, and watch it appear.
Make a registration form for the spaghetti evening on 12 September at the parish hall. Ask for the name, the email address and how many portions.
A few seconds later the form exists on your site, as a draft, with its own page - ready for you to look over and publish.
The same panel works on a form you already have. Open it in the builder and ask for a change:
Add a question asking about dietary requirements, and make the email field required.
The panel sits beside the builder rather than over it, and the form updates in place while you watch: a question the assistant adds appears in the canvas, briefly marked, without the page reloading and without losing the thread of the conversation.
What you need
- LocalForm Pro, and WordPress 7.0 or later - the AI client is part of WordPress from 7.0.
- An AI provider connected to your site. Install a connector plugin for the provider you use - Anthropic, OpenAI or Google - and add your API key to it.
- Administrator access. Building forms is an administrator's job, and so is this.
LocalForm holds no API key of its own and charges nothing for the feature. It asks whichever provider your site is already set up with, so what you spend is what that provider charges you, and nothing passes through us.
If no provider answers, the panel says so and lets you try anyway - some setups will not list their models but generate text perfectly well, and the error from a real attempt tells you far more than a guess made beforehand.
Where to find it
- Forms → Build with AI, next to Add New, to start something new.
- The sparkle button in the builder's top bar, to change the form you have open.
Type your request, press Enter, and the panel shows each step as it happens - looking at your forms, reading one, saving one - then answers in a sentence or two saying what it did.
What it can and cannot do
It works through the same three abilities an outside assistant uses over MCP, which means:
- It can list your forms, read any one of them, and create or update one.
- Everything it saves goes through the same validation as the builder. It cannot store something you could not have built by hand.
- Reconfiguring a form never deletes the responses already collected.
- It cannot delete a form, read a submission, or touch anything else on your site.
New forms are created as drafts unless you ask for them to go live, so nothing appears to your visitors before you have looked at it.
Good requests
The more you say up front, the less there is to correct afterwards.
| Instead of | Try |
|---|---|
| "Make a signup form" | "Make a signup form for the choir: name, email, voice part (soprano, alto, tenor, bass) and whether they have sung before" |
| "Add a date" | "Set the event date to 12 September at 19:30, at the parish hall" |
| "Add prices" | "Charge €25, or €15 for students - as separate rates" |
Asking in your own language is fine: labels and messages are written in your site's language unless you ask for another.
Things worth knowing
Check its work. It is a good first draft, not a final one. Read the form before publishing - especially the field names, which is what your responses are stored under.
Save your own edits first. Each change the assistant makes is saved to the form, and the builder then shows what was saved. Anything you had typed into the builder and not saved is replaced by it, so save before you ask for a change.
One conversation at a time. The panel remembers the conversation for half an hour. Closing the panel and reopening it starts fresh.
It stops if it goes in circles. A request it cannot make sense of ends with a message rather than an endless loop.