Overview
Turning a watched cloud folder into entity records, with a human approving every value before it lands.
An integration flow watches one folder in a connected cloud storage account and turns the documents it finds there into entity records. A flow reads each document, pulls out the fields you asked for, and holds the result for someone to check. Nothing reaches a record until a person approves it.
This is how a folder of resumes becomes a candidate list, or a folder of signed contracts becomes account records, without anyone retyping what is already written in the file.
How a flow works
Each flow is bound to one folder in one connected account, and carries its own list of fields to extract and its own mapping onto an entity. A run walks the folder, reads whatever is new or changed since last time, and produces one pending extraction per document.
Two rules shape everything else. One document produces one record, so a flow never fans a single file out across several records. And a re-run updates rather than duplicates: Auron remembers which record came from which file, so the second time a document is processed it revises the record it created the first time, even if the file has since been renamed.
The approval gate
Extraction is automatic; writing is not. Every extracted value waits in the flow's Review tab until a reviewer approves it, and approval is the only path to an entity record. A run that finds ten documents writes nothing at all on its own.
This is deliberate. Reading fields out of a document is a judgement call, so each extracted value arrives with a confidence score and the snippet of source text it came from, and a reviewer can correct anything before it is written.
Getting there
Connect a source
An owner or admin enables the storage integration for the organization, then each person connects their own account. See Connect a source.
Create a flow
Pick the folder, set how often it runs, define the fields to extract, and map them onto an entity. See Create a flow.
Review and approve
Check what was extracted, correct anything wrong, and approve. See Review and approve.
Where this is managed
Flows live in the console under Integration Flows. The connections they run on are managed separately under Settings as Integrations. Supported file types, schedule options, status meanings and processing cost are collected in the Reference.