Documentation Index
Fetch the complete documentation index at: https://filla.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
What it is
Every form editor has a built-in AI assistant. It can read your current form, look up your Airtable base schema, and search the Filla docs to answer questions like “which fields are required on page 2?” or “how do I lock the Email field after the user picks a country?”. The assistant explains and suggests. It does not modify your form or Airtable on its own — it tells you the exact path to click instead. For an AI that builds forms by writing to Airtable, see Build a form with AI.Opening the assistant
The left sidebar in the form editor has two modes — Fields and Ask AI. Switch between them with the segmented control at the top of the sidebar. You can also press Cmd/Ctrl+K anywhere in the editor to jump straight to AI mode and focus the chat input. When the sidebar is collapsed (rail mode), the same two icons appear stacked. Click the wand to expand into AI mode.What it can answer
| Topic | Example questions |
|---|---|
| Your current form | ”How many fields are on page 2?” “Which ones are conditionally hidden?” “What’s the form’s accent color?” |
| Your Airtable base | ”Does my Contacts table have a Newsletter field?” “What field types are available on Orders?” |
| Filla features | ”How do I lock a field after submit?” “Can I send a confirmation email with a download link?” |
| Setting paths | ”Where do I turn on duplicate prevention?” — the assistant replies with the exact UI path. |
How it works
The assistant uses three tools internally. Each call shows up as a small status row in the chat so you know what it’s doing:| Tool | When it runs |
|---|---|
| Reading your form | Any question that depends on what’s currently on the canvas. |
| Reading your Airtable base | When you reference a specific Airtable column the assistant hasn’t verified yet. |
| Checking the docs | For Filla-feature questions where it shouldn’t guess. |
tbl… or fld… IDs. Pages are numbered (1, 2, 3) instead of identified by internal IDs.
Anti-hallucination guardrails
The assistant is constrained to only describe UI elements that appear in the docs it just fetched. If a label isn’t in those docs (or is explicitly listed as a known hallucination), the assistant will say so rather than invent something. When the answer is found, it paraphrases atomic key facts from the doc rather than synthesizing. This means: if the assistant says a button or setting exists, you can trust it’s real. If it says it can’t find something, that’s an honest answer — re-phrase your question or check support.What it won’t do
- Apply changes for you. The assistant cannot add, remove, rename, or re-configure fields. It tells you the path; you click it.
- Modify your Airtable base. No table or field creation. For that, use the AI form builder.
- Send messages or trigger automations. Read-only and suggestion-only.
Conversation lifetime
A new thread starts every time you open the editor. The assistant remembers everything within that session, but doesn’t persist context across editor reloads — when you come back, you start fresh. This avoids stale assumptions about a form you may have just changed.Common questions
Does this count toward my plan limit?
Does this count toward my plan limit?
No. AI conversations don’t count toward your records limit. Only Airtable writes do — see Billing for what counts.
Can the AI see my submissions?
Can the AI see my submissions?
No. The assistant has read access to your form’s structure (pages, fields, settings) and your Airtable schema (table and field names + types). It does not read submitted records.
Why does the AI sometimes search the docs first?
Why does the AI sometimes search the docs first?
Some questions (“does Filla support partial submissions?”) need an authoritative answer rather than an educated guess. When the assistant isn’t sure, it checks the docs and replies with what it found.
Can I ask it to build something new for me?
Can I ask it to build something new for me?
The in-editor assistant is read-only — it can describe how to build it but won’t make the change. For form-level structural changes (new tables, fresh forms), open the builder via the New Form → Ask AI to build it entry point.
The assistant is referencing a field by an old name
The assistant is referencing a field by an old name
The form editor refreshes its base schema when you sync fields. If you renamed something in Airtable recently, click Sync fields in the editor toolbar — the assistant will read the new schema on its next tool call.