The form builder and the report builder each include an AI assistant, and a third assistant helps write webhook preprocessing scripts. You describe what you want in plain language, and it proposes a set of changes. You review the proposal, then apply it or discard it — the assistant never changes your work on its own.
How it works
Open the assistant from inside the builder and type a request the way you would explain it to a colleague: "Add a site name, an inspection date, and a pass or fail status," or "Group the expenses into a table and total them at the bottom." The assistant reads what is already on the canvas, works out the change, and shows you a proposal — a short summary of what it will add or adjust.
From there you have two choices:
- Apply changes — the proposal is written into the builder so you can see it in place.
- Discard — the proposal is dropped and nothing changes.
Applying is not saving. The change lands in the builder just like an edit you made by hand, and nothing reaches your field users or your reports until you save the draft (for a form) or save the report. If you apply a proposal and change your mind, Undo reverts it.
It builds within the rules
The assistant proposes changes through the same checks the builder applies to your own edits. It cannot hand you a field setup the builder would reject, a formula that does not parse, or a report template with broken merge syntax — a proposal that would fail those checks is not offered. You get the speed of describing a change in words without the risk of breaking a working form or report.
It also stays on task. The assistant is there to build forms and reports; it does not answer unrelated questions or take the conversation elsewhere.
What you can ask for
In the form builder:
- Add fields of any type — text, numbers, dates, lookups, photo or signature capture, repeating tables.
- Set up conditional visibility, formulas, and read-only computed fields.
- Filter a lookup field by other answers, or show and hide individual choices in a list field based on earlier answers.
- Set a display format on a number field — thousands separators, currency, or percent.
- Reorganize a form into sections or pages, or adjust an existing field.
When you ask for pages, the assistant builds them. It may also suggest splitting a long form into pages, but it never adds pages on its own — the layout stays as you built it unless you ask for the change.
In the report builder:
- Lay out a report from a description — headings, tables, totals.
- Pull in fields from your forms, including repeating tables, and reference fields from more than one form in a single template.
- Adjust an existing template — change the layout, add a section, format a value.
On a webhook subscription:
- Describe how you want an event reshaped before it is delivered, and the assistant proposes a preprocessing script for you. It checks the script against a real sample of each event you subscribed to and shows the result per event before you apply it. See webhooks for what preprocessing does and its limits.
Because the assistant reads the current state each time, you can build in steps: ask for a first pass, review it, then ask for the next change.
What it sends, and where
The assistant runs on a model from Anthropic, so the work does not stay inside your workspace. Each time you send a request, three things go to Anthropic: your message, the form, report, or webhook definition you are working on, and any image you attached to that message. Anthropic is named on the subprocessor list with the rest of the services that handle customer data.
Your records do not go with it. The assistant reads the design you are building, not the submissions collected against it — with one gap worth knowing: nothing stops you pasting a screenshot of live record data or typing someone's details into the message box, and if you do, that goes too. The panel carries a one-line reminder above the message box for the same reason. Keep record data and personal information out of the conversation.
Previous images are not resent. An image belongs to the turn you attached it to and is not replayed on later turns.
Turning it on
The AI assistant is off by default. Turning it on for a workspace is done by the team that operates the platform, not from workspace settings — ask your FieldScroll contact or contact support. Until it is on, the assistant does not appear in the builders.
To keep usage predictable, there are limits on how often the assistant can be used and how much it can do in a day across your workspace. If you reach a limit, the assistant tells you and you can try again shortly.