What is behind every agent

Nothing is uploaded by hand.

The agent reads the documents where they already are, consults the tables you let it read, and writes the results back beside them — on our servers or on the client's own machine.

• I

  A folder or an SFTP

  Point the agent at the folder the documents already arrive in — SFTP or FTP, S3, Azure, a shared folder. It reads each one from there and writes the results back next to them: the CSV, the JSON and the report PDF into a processed folder, one run at a time. The inbox is read, never emptied.

  fatture/inbox → fatture/processed

  Read the data sources guide→
• II

  The company's database

  A read-only role on the ERP's Postgres or MySQL is all it needs. The tables the agent may consult are saved once — the open purchase orders, say — and read during the run to check what it extracted. The agent never writes to your database.

  ordini_acquisto · stato = 'aperto'

  Set up a connection→
• III

  On the client's own PC

  The same agent runs on the client's own machine with afb-runner, on a local folder and the local database. The documents never leave the room; only the counts and the seat come back to the platform. A signed definition keeps it valid for a fixed period.

  afb-runner doctor → afb-runner ui

  See local runs→