Skip to main content
An agent reads either the fields you add as inputs, or the entire row when its prompt names none. What it hands back is just as deliberate: name each output field and it becomes its own column once you deploy it.
The Add agent to table dialog with a Map input fields option bound to table columns, and an Outputs section naming a column per output field.

The Add agent to table dialog, mapping inputs and naming output columns.

​
Add an input

1

Add each value the row provides

In the Configuration panel’s Inputs section, click Add input and name it. Or click Suggest inputs from prompt to have Oneprofile read the prompt and add what it already asks for.
2

Or read the whole row instead

Turn on Use the whole row to hand the agent every column rather than naming fields one at a time.

​
Shape what it returns

The Outputs section declares the fields an answer is made of, either as repeatable named fields or, behind an advanced toggle, a raw schema.
1

Name each field

Click Add output, give it a name and a type, then click Add description if it needs more than a name to explain it.
2

Or generate them from the prompt

Click Suggest outputs from prompt to have Oneprofile propose fields from what the prompt already promises to return.
3

Or write a raw schema

Switch from Fields to JSON Schema to declare the output contract directly, checked against every strict-mode rule on save.

​
See each field become a column

1

Map or hand over the row

Click Add to table, choose a table, then map each input to a column. Click Match inputs by name to fill in the obvious ones.
2

Name the column

An agent with one output field adds a single column. One with several folds them into a group behind a parent column, and you can rename or skip any field before adding it.

​
Good to know

Yes. Deploying is a per column choice. Mapping columns on one table and handing over the whole row on another both work, as long as the prompt names no input.
Only when the prompt does not reference any input by name. Otherwise every input needs a column mapped to it, so the dialog maps rather than hands over the row.
The dialog warns you and runs will skip a row until that column is filled in or you remap it to another one.
Yes, by dragging the handle beside a field or using the arrow keys once it has focus. Order matters: it decides the order the fields fan out into columns.
Renaming is free text in the deploy dialog, so give each one a distinct name before adding the column. A collision with a name already on the table is refused.

​
Next steps

Build an agent

Start an agent and write the prompt these inputs and outputs belong to.

What agents cost

See how what an agent reads and returns affects the price.