AI form automation: a form that starts the work and shows the result
Turn a web form into an AI employee: each answer runs a flow that looks things up, decides and shows the result on the page, by email, or to your team.
Part of the guide AI employees
AI form automation means a form does more than collect answers: the moment someone presses Send, an AI employee picks up what they typed, looks things up, makes a decision and answers, often while they are still on the page. In xMap Flows the Form page block gives you the form itself, a page you share or place on your website, and each answer runs a flow once with the answers as one item.
This is for marketing teams that want forms which give something back, sales teams that want enquiries arriving already qualified, and operations teams that take requests from customers or staff. It covers what the form can ask, the three ways it can answer, two examples and the mistakes that cost leads.
What the form can ask
A Form page holds up to 12 fields. Each has a label, a help line, whether it is required, and a kind: short text, long text, number, email, phone, a choice from your options, a place, or a date. A place answer is looked up for you, so the next blocks can search around the address someone typed. Every answer reaches the flow under its own field name, such as {{company_name}}.
Answers are checked on the server as well as on the page: a required field left empty, an email that is not one, a choice you did not offer, or a place that cannot be found is sent back to the person to correct.
Three ways to answer
- A thank-you message, when the work happens behind the scenes, for example a lead scored and handed to sales.
- The result on the page, when the flow finishes within about a minute. Put a Reply after the work to show your own words, such as the nearest depot's name. A longer run is emailed instead.
- The result by email, sent to the address typed in the form's first Email field, for a report or a list.
Example one: a free local market check (made up)
A coworking operator in Singapore wants leads from small businesses thinking about where to base themselves. It offers a free check on its website: type your kind of business and a postcode, and see who else is around.
- Form page: business type (a choice of ten), the postcode or address (a place), and a work email.
- Travel area: 10 minutes on foot from the place given.
- Nearby places: places of the chosen type inside that area, from xMap's places database.
- xMap LLM, the whole list: two friendly sentences on how busy this kind of business is around the address and what that could mean; only the figures given.
- Reply on the page with the sentences and the count; a copy to the sales team by Email.
The visitor gets something useful in seconds, and the sales team gets a warm lead with the area already looked at.
Example two: requests sorted on arrival (made up)
A facilities company in Lisbon takes maintenance requests from the buildings it looks after through a form: the building, the kind of problem, a description and a phone number. An AI router reads the description and sends each request down one of three outputs (Urgent, Planned, Question), with a reason. Urgent goes straight to the duty engineer's phone by message, Planned to the scheduling sheet, Question to the help desk. The page thanks the tenant and says the request was received.
Mistakes that cost answers
- Too many fields. Every extra question loses people. Ask only what the flow needs to do its work; the rest can come later.
- Free text where a choice would do. A choice of business types gives the search a clean value; a free box gets spelling the next block cannot use.
- Promising an instant result for slow work. If the flow does a lot, choose the email answer and say on the page when it will arrive.
- Forgetting the form needs a live flow. The form takes answers only while the flow is live and its Form page is on. Test runs use example answers made from your fields.
How to set it up
- Make a new flow and add Form page as its trigger.
- Add the fields, in the order a person would answer them, and write the intro under the title: what they get when they send it.
- Add the blocks that do the work, then Reply or an Email.
- Choose what happens after sending, switch the Form page on, and deploy the flow.
- Copy the link from the flow's menu, under Form page link, and put it on your site.
The same fields also describe the flow when you offer it as a tool to AI assistants, so one setup serves both. A chat is the other way in: the legal intake assistant takes enquiries as a conversation, and score new leads from a sheet suits enquiries that already land in a sheet. For more on flows that start themselves, see the workflow automation guide.
Questions
Can I put the form on my own website?
Yes. Each form has its own link you can share or place on your site, found under the flow's menu, Form page link.
What if the work takes longer than a minute?
Choose the email answer. A run that does not finish within about a minute is emailed instead of shown on the page.
Are the answers checked?
Yes, on the server too. Missing required fields, wrong emails or numbers, choices not offered and places that cannot be found are sent back to the person.
Can the form route requests to different teams?
Yes. Put an AI router after it to send each answer down an output you name, or a Branch when a field already decides it.
Templates that do this
Read next
More on ai employees and automation · Every article · Templates