Fields & value sources
A field is one value a template produces. Its inputs say where the value comes from: a question, the document, a fixed text, the case, or the delivery that brought the file. Its outputs say what stamps on the page, and the field type shapes both.
Every value a template captures or prints is a field. You pick a field type to shape the output. You pick an input source to tell the app where the value comes from. If you are building your first template, start with Templates and come back here when a field needs more than the default.
What a field is
A field is one value the template produces. The field card has an Inputs section labeled Where does the value come from? Click Add input to add a source.
The card has an Outputs section to control what stamps on the document. Click Add output for derived values. Outputs hold Write zones. You click Add write zone to position the text.
Extracted inputs hold Read zones. You click Add read zone to tell the AI where to look.
Pick a type from the toolbar. The types include Text, Number, Date, Select, Signature, Checkbox, and Image. The plus menu holds Address, Options, and Batch.
The field drops with a static input reading SAMPLE VALUE and a write zone. Every field stores its value under a stable key. Renaming the display label never moves the data.
Field types
Types guide the output. A date field forces the AI to return a parseable YYYY-MM-DD date. It prints as MM/DD/YYYY. A number field does not force a number during AI extraction.
Checkbox is a boolean. Select picks from a fixed list. Options renders radio or checkbox choices. Image uploads once and reuses logos or stamps.
Signatures are adopted or drawn from the client portal or the Data tab. The AI never extracts signatures from a document.
Use Batch for one value per case when this template runs on many cases at once. You set a fixed count using the Rows: counter. It renders one row per selected case in a Pro batch fill.
Higher plans unlock dashboard views. Address fields feed the Map view. Date fields feed the Calendar view. Numbers feed Analytics.
Where a field gets its value
Pick the input source under Value source.
- Form field: A person types this into the Form card on the Data tab, or on a case, or in the portal. Form fields include placeholder, help text, and required settings.
- Extracted: The AI reads the value off the document. You add read zones or leave it open.
- Static: The field uses the exact same text on every run.
- From case: The field reads a value another document already saved to the case. It matches by field name.
- From the delivery: The field reads information from the incoming email or Google Drive folder before a case exists.
For case sources, you add an instruction if the name is not enough. The app pulls this fresh on every run and never saves it again.
Delivery sources vary. Email offers subject line, sender address, and message body. Drive offers file name, folder name, date added, and date last changed.
The Drive dates sort and compare like real dates. Pick the part under Delivery part. You leave it empty or add an instruction to extract a piece.
The message body always requires an instruction. The field stays empty if an email delivers a file to a template expecting a Drive folder.
New fields default to a question if no document is attached. The app says No document attached yet. New fields act as form questions until you upload a PDF or image. The Value source picker stays hidden until you attach a file.
Identifier fields
Identifier fields route files to the right case. Pick the ID type. The hint says Files carrying this value route to the same case.
ID fields use an extracted, question, or delivery source. They do not accept a static or case source. The app spells the consequence out under the picker.
Every email from one sender address joins one case. Every file in a watched Drive folder joins a single case.