JMN Field Manual

02.1 — Building Agents

Properties Explained

A property is a column. Every property points one of two directions — in or out — and that single choice decides everything else about how the column behaves.

Input properties

An input property holds a file. Drop a document into the cell and it's ingested in the background: text extracted, split into chunks, embedded, and stored — ready to be queried by any output property in the same row.

Supported file types, currently:

ExtensionTreated as
.pdfPDF document
.docxWord document
.txtPlain text
.mdMarkdown

Note

Drop more than one file into the same input cell and JMN AI spins up a Collection — a sub-agent with one row per file, so you can analyze each document individually instead of all at once. See Collections (Sub-Agents).

Output properties

An output property is a question, asked once and run against every row. What answers it — a model, a script, a document export, or a person typing directly into the cell — is controlled by the property's tool setting, covered in full in Tools & How They Work. What shape the answer takes is controlled separately, by output type.

3.1
The output type dropdown on a property

FIG. 3.1 — Every output property has one of seven types.

Output typeWhat the cell holdsEnforced automatically
TextFree-form written answer— (default, no constraint)
NumberA single numeric valuePrompt instructed to answer with only a number
DateA calendar dateMust come back as YYYY-MM-DD
TagOne label from a fixed listMust match exactly one of the property's Tag Options
JSONA structured JSON valueNo prose, no markdown fences — valid JSON only
TableRows and columnsJSON (list of objects or list of lists), rendered as a table
FileA generated, downloadable fileSet automatically when the property's tool is Export

Note

Tag is the one type a human can correct after the fact, without re-running the AI — and the only type with a fallback setting for "if no match is found" (keep the cell empty, or fall back to whatever the model said). Both are covered in Tagging & Classification.

What can't change quietly

Editing a property's prompt or output type after cells have already run doesn't silently recompute them. Anything downstream gets marked stale instead, so you decide when to re-run rather than discovering a column has changed underneath you. Full mechanics in Keeping Results in Sync.