Agents do the paperwork.
You handle the exceptions.
Agents read the emails, PDFs and scans that arrive, check them against your own systems and enter the result. Unclear or costly cases go to a person.
Each document type gets its own agent.
Four agents at a freight forwarder. Each reads one kind of document and writes the result into the systems the team already uses.
A shipper emails a transport order as a PDF. The agent reads pickup, delivery, dates and goods and creates the order in the transport system.
The agent compares each invoice with the rate agreed for the shipment. Matching invoices are booked, and a deviation above the limit waits for approval.
Drivers upload signed delivery notes as scans. The agent attaches each scan to its shipment and records any damage noted on the paper.
At 7:00 an agent collects every case that waited for a person yesterday and posts the list with reasons to the dispatch channel.
From typing documents to deciding on exceptions.
Today your team opens, types and files every document. With agents, people see only the cases an agent puts in front of them.
Sorting the inbox
Today, by hand: Someone opens every email, works out what the attachment is and passes it on
With agents on connic: Every new email starts an agent, and the agent reads the attachments itself
See how much paperwork the agents take off your team.
Every document is recorded with its input, result, duration and cost, so these figures need no extra tracking.
Share without a person
Compare the cases a person approved or flagged for review with all documents in the period.
Cost per document
Each run shows its model cost, broken down per agent, so you see what one invoice or one order costs.
Failed checks
Failed runs show the full error first, and attachments that couldn't be read are listed with the reason.
Processing time
Each agent's page shows how long its runs take. Time spent waiting for an approval shows separately in the run.
Every entry is checked, approved where it matters and on record.
The agent returns only the fields you define and uses only the tools you give it. Above your limits, a person decides.
- Results in your format
- You define the fields, types and allowed values of a result, and connic checks every result against them.
- Costly cases wait for a person
- A booking waits, for example when an invoice is more than your limit above the agreed rate. The reviewer sees the values the agent wants to enter and approves or rejects them.
- A record of every document
- Each run keeps the document, its result and every value the agent sent. The audit log shows who approved what.
- Tested before every change
- Sample documents become test cases that run before every release. A failing case stops it.
The rules live in two files your engineers can review.
The agent file names the output schema and the approval rule. The schema file lists every field the agent may return.
- Output schema
- Fields under
requiredmust be present,enumlimits a field to fixed values, andadditionalProperties: falserejects anything else. - Approval rule
- The booking pauses when
deviation_euris above 50. Below that, the agent books the invoice on its own. - Flag for review
- The prompt says when to set
needs_review, and the run filteroutput.needs_review == truelists those documents.
version: "1.0"
name: carrier-invoice-check
type: llm
model: connic/gemini-3.8-flash
description: "Checks carrier invoices against the agreed rate"
system_prompt: |
Read the carrier invoice attached to the email.
Look up the agreed rate for its shipment, then book it.
If a field is unreadable, set needs_review and don't book.
tools:
- tms.get_agreed_rate
- erp.book_carrier_invoice
output_schema: carrier-invoice
approval:
tools:
- erp.book_carrier_invoice: param.deviation_eur > 50
timeout: 86400
on_rejection: continue{
"type": "object",
"properties": {
"invoice_number": { "type": "string" },
"shipment_id": { "type": "string" },
"amount_eur": { "type": "number", "minimum": 0 },
"deviation_eur": { "type": "number" },
"status": {
"type": "string",
"enum": ["booked", "held", "rejected"]
},
"needs_review": { "type": "boolean" }
},
"required": ["invoice_number", "amount_eur", "status"],
"additionalProperties": false
}Keep exploring
- ConnectorsLet a mailbox or upload bucket start the agent and hand the result to your ERP.
- ToolsGive the agent functions that look up rates and write bookings through your own systems.
- TestingTurn real sample documents into test cases that run before every release.
- BridgesReach the transport system and ERP in your network without opening it to the internet.