Browse the Knowledge Center
Workflows
AI CRM Agent: inputs and outputs
Controlling what the AI CRM Agent can read and write. Under Input, each related record has a switch: person, company, opportunities, notes, tasks and AI meeting notes, with chosen fields and first, last or all for lists; fewer inputs means less noise and fewer hallucinations. Under Output, choose the fields it fills, written back to the record, with Required forcing a value and Reason showing why in the run without saving it. The updated record becomes a variable for later steps.
Transcript
Next, decide what the AI CRM Agent can read, and what it can write. Under Input, each related record has its own switch: the person, their company, linked opportunities, notes, tasks and AI meeting notes. Open one to pick its fields, and for lists, choose the first, the last or all records. Turn on only what's relevant: less noise, fewer tokens, fewer hallucinations. Under Output, choose the fields the AI fills. Its answers are written straight back to the record, here the person's Intent score. Tick Required, and it must give a value whenever it writes. Turn on Reason to see why it chose what it did, shown in the run and never saved. The updated person then becomes a variable for every step after it. Each Friday, Alex asks Claude to narrow his AI step. Claude leaves it reading two inputs and writing one. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so keep it small, then give it a bigger job each week. In Vetta, check the switches, then activate it yourself.
Read the article: AI agents in workflows