Production monitoring · Autessa Evaluations
Export and sync
Conversation history and evaluations leave Autessa whenever you need them. Export as JSON (full details, logs and evaluations) or CSV (a summary table), or set up Conversation Sync to write every closed conversation into a database table automatically for analysis and labeling.
The problem
Your analysts want the data
Evaluation data is most useful when it can be joined with tickets, revenue and labels in your own tools. Copying it out by hand is slow and stale.
What you get
- Export the last one, two or three months.
- JSON includes full conversation details, logs and evaluations.
- CSV is a summary: date, version, message and tool counts, API key and conversation ID.
- Conversation Sync writes closed conversations into AutessaDB tables while the configuration is on.
- Choose the agents (or all), a match column for the conversation ID, and the column for the conversation JSON, with or without tool calls.
- Fill extra columns from variables like @@{conversationId}, @@{closeDate}, @@{agentVersion}, @@{channel} and @@{language}.
- Synced tables can run triggers, power knowledge bases or feed scheduled reports.
How it works
How does export and sync work in Autessa Evaluations?
Export once
Open the export dialog, pick a range, choose JSON or CSV; the file downloads immediately.
Or sync continuously
Choose Sync with AutessaDB, create a configuration and pick the agents.
Map the table
Pick the table, the match column and the conversation JSON column, and whether unmatched conversations insert new rows.
Map extras and save
Fill more columns from sync variables. New conversations sync automatically.
Every option
Export and sync options
| Option | What it does |
|---|---|
| Time range | Last one, two or three months. |
| JSON / CSV | Full details with evaluations, or a summary table. |
| Agent filter | Specific agents or all, optionally including sandbox conversations. |
| Match column | A text column holding the conversation ID. |
| Conversation JSON | With or without tool calls (including them increases stored size). |
| Insert or skip | Upsert unmatched conversations, or skip them. |
| Sync variables | @@{conversationId}, @@{closeDate}, @@{agentId}, @@{agentVersion}, @@{apiKeyId}, @@{channel}, @@{language}, @@{conversation}, @@{shortened_conversation}. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| People who can see the agent’s history | Export what they can see and set up sync into tables they can write. |
FAQ
Questions about export and sync
Can I export evaluations?
Yes. A JSON export includes full conversation details, logs and evaluations.
Can conversations land in a database automatically?
Yes. Conversation Sync writes every closed conversation into an AutessaDB table while the configuration is enabled.
Does sync include tool calls?
Your choice. Including them can significantly increase stored size.
100% customizable, code and all
Make Autessa Evaluations fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours