Generate a form from a description
Aglyn AI is in beta. It is available today on every plan that includes it, and it is still changing as we improve it. Beta means you can use it now, while what it builds and the steps on this page may still change.
An AI build job can make a form from a brief, such as "a quote request form for a roofing company". The job proposes a plan first, and builds once you confirm it: the fields a visitor fills in, the answers the form needs, a marketing consent box when the form asks for an email address, and where each submission goes. The form follows the building rules, and one more of its own: what the form's design draws and what the form declares always agree, so every field has its own name and every submission arrives with all of its answers.
The form arrives as a new draft on the Forms page, and Open draft on the job opens the form's page. No page on your site places it, so nothing on the live site changes. It counts against your forms allowance like a form you create yourself, and when your plan has no room for another form the job says so before it starts, not after it has spent anything.
Describe the form
Open Forms for the site and choose Create with AI, beside Create Form. Write what the form is for in one box: who fills it in, what you need to know from them and what should happen with each submission. Then choose Plan the form.
The job proposes its plan before it builds anything. The window shows the plan when it is ready: choose Confirm plan to build the form, or Cancel job. Open AI jobs follows the job in the Assist panel instead.
What the form gets
- Fields of the types a form supports: text, email, multiline, dropdown, radio choice, checkboxes and star rating. Each has a label, and is marked Required only when the form cannot do its job without the answer. They are built from the Besigner's separate form elements, so you edit and style them like any field you add yourself.
- Marketing consent. When the form asks for an email address, it gets the Marketing consent field, the same one the Besigner's element picker adds: a single Checkbox beside the words Email me news and offers, left unticked and named as the form's Marketing consent field. A visitor who ticks it is recorded as consenting; submitting the form is never consent on its own. You can reword the text beside the box on the form.
- Routing. Every submission lands in the Inbox. When your brief describes each submission as a sales lead, the form also files a lead in CRM → Leads, which you can switch off on the form's page. When your brief asks to add people to an email list, the job tells you how: add an action on form submissions that enrolls the people who tick the consent box. The job never picks a list for you, and it never reads your lists, contacts or submissions.
What a form cannot collect
A form collects text, choices and ratings. When your brief asks for something else, such as a file or photo upload, a signature or a payment, the form leaves it out and the job says so beside Open draft. For a roofing quote request that asks for photos of the damage, for example, the form asks for a written description of the damage instead. A fact the brief did not give is left out of the form. If the form still shows one in square brackets, such as a label naming your studio, the job lists it for you to fill in before the form goes on a page.
Nothing is live until you place it
The job creates the form and nothing else. Review it on its page and in the Besigner, then place it on a page with a Form element when you are ready. A form placed on a published page starts collecting straight away, so check its fields and its consent box first.
Who can use it
Build jobs need the Generate with AI permission, and your plan must include forms. See who can use AI assist.