Transcript
Connection Hub
The Connection Hub connects DocReveal to your other tools. It opens from the plug icon in the header. The tiles count your connections and banks, what needs attention, the catalog and your custom connectors. Four tabs below: your connections, the Service catalog, Custom connectors and Activity. Every connection shows its state, how long it's valid, and who uses it – the Keldmoor ERP connection serves a flow and an agent.
Service catalog
New connections start in the Service catalog – apps, banks and custom connectors, filtered by type, sign-in or category. Click a service to see how you sign in, what you'll need, and what it can do – IMAP brings four actions and a trigger for new e-mail. Connect asks for exactly that: a name – AP mailbox – the server and the sign-in. Secrets are stored encrypted and never shown again.
Banks
Banks have their own filter in the catalog – narrow them down by country to find yours. Corvane Bank connects with access from your internet banking – free, read-only, no payments – and brings accounts, balances, transactions and statements. Paste the API token from your internet banking and the date it's valid until – DocReveal reminds you before it expires. Connect – and DocReveal loads your accounts: the operating account in dollars and the EUR account.
Connection detail
Each connection opens its details: who created it, how long it's valid, and – for a bank – the accounts it reads. Used by shows what depends on it – the bank feeds the Daily bank statement flow. The Keldmoor ERP connection serves a flow and the Invoice triage agent. And nothing breaks by accident: while an enabled flow uses a connection, it can't be deleted.
Integration flows
Now let's put the bank connection to work. In Integration Manager, the Daily bank statement flow runs on a schedule. Edit it: the trigger is a schedule – every day at 7:00 UTC, with the next runs listed below. A Date Helper step works out yesterday: it takes today's date and subtracts one day. Then the Corvane Bank step, Statement for a period, uses the bank connection and the operating account. From and To are both yesterday, and the format is JSON. Last, Upload document to DocReveal files it into the Bank folder, one subfolder per month, with the Bank statement label. It has run every morning since – each run with its four steps, down to the file it uploaded.
File Manager
In File Manager, the statements land in the Bank folder – one per day, recognized as Bank statement and labeled. Each one is processed like any other upload: a summary with the day, the movements and the closing balance, then mapped and indexed in the knowledge graph. Open it, and every movement is there as data – including the payment of INV-88121 to Stavlund.
RAG chat
Because the statements are documents now, you can ask about them. In RAG chat: which supplier invoices did we pay last week, and which are still open? The chat matches the statements to your invoices: INV-88121 paid as approved, a Czech invoice paid in euros, and one payment with no invoice in DocReveal at all. It lists what's still open – including the three disputed invoices on hold – and every point links to its source. It even suggests what to do next – ask Oakhurst Packaging for the missing invoice.
Agents
Agents use the same connections. In the Invoice triage agent's Capabilities, Add a tool offers Connectors. Email (SMTP), the AP outbox connection and the action Send email – marked sensitive, because it changes data. Sensitive tools follow their group's policy – here, Require human approval. Custom connectors work the same way: the agent can look up a purchase order in the ERP. A mailbox can start an agent, too: the Mailroom agent checks the AP mailbox every five minutes.
Custom connectors
When a service isn't in the catalog, build your own connector. Keldmoor ERP was imported from the ERP's OpenAPI file. In Connector Studio, set the service address – the connector may only call that host – then the sign-in: an API key in a header. Each action is one call to the service. Test it with the real connection – a successful test unlocks publishing. Every check is green – publish version 1, and its actions appear in the flow designer and in agent tools. So the approved-invoices flow now creates the payable through the connector, every field mapped from the invoice.
Activity
Bank access doesn't last forever. Before a token expires, the connection moves to Needs attention – and a notification reminds you. Back in the hub, Renew asks for the new token from your bank – the connection and every flow using it stay in place. One click – valid until March 2027, and nothing needs attention. Activity records who created, renewed or published what, and when – including the system's own expiry warnings. That's the Connection Hub – connect once, and every flow and agent can use it.