Integrations.
A pipeline written for one system specifically. It lands that system's data in your own warehouse overnight, modelled and joinable, so every other connection can be read next to it.
Data comes in, so it can be reported on, trended and watched.
It lands rows, not summaries
Invoices, bank transactions, timesheets, stock movements. The underlying records, not a cached total someone else calculated. That is what makes a figure joinable to a different system later.
It refreshes on a schedule
Twice daily, plus an on-demand refresh you can fire by hand from the connections screen when you have just posted something and want to see it.
It carries your history
Not just today's balance. The trend line, the same month last year, and the movement in between - which is the only way a number means anything.
It is maintained
Every one of these is hand-written against a specific API, and those APIs change without warning. When a vendor ships a breaking change on a Friday, fixing it is our problem rather than yours.
Where this usually comes from.
Anything you need trended over time, watched by a Pulse, or joined to another system. If the answer involves the word "since", it needs an integration.
A one-off question about a system nobody else in the business uses. An Action MCP or a dataset will get you there faster without waiting for a pipeline.
The whole list, by what it does.
Generated from the connection registry, so this is what engineering has shipped rather than what marketing hopes. Each one has its own page with what it lands and the questions it answers.
Six kinds of connection, and they are not interchangeable.
Picking the wrong one is the most common mistake people make in their first fortnight, so here is the whole set in one place.
EVA reaches into another system and does something
Your own SQL, read directly and joined to everything else
Spreadsheets and CSVs that never had a system to live in
Contracts, leases and policies she can read and cite
Public pages worth watching, read on a schedule
Integrations, answered.
How often does an integration refresh?
Twice daily, plus an on-demand refresh you can trigger by hand from the connections screen at any time. Reports and Pulses always read the most recent successful refresh, and the screen shows you when that was.
What happens if my system is not on the list?
Tell us and you will get a straight answer about whether it is built, in the queue, or unlikely. Some systems can be reached over an Action MCP in the meantime, which answers live questions but will not give you history or Pulses.
Where does the data actually go?
Into a database in your own region that belongs to you - not a shared tenancy. It is never used to train any model, ours or anyone else's, and it is removed entirely if you leave.
Does connecting an integration change anything in my system?
No. An integration only reads. Nothing is written back to your ledger, your roster or your stock system. Writing outward is what Action MCPs do, and they are a separate, deliberate choice.
Connect one and see.
Bring your messiest system and your simplest one. Fourteen days is enough to find out whether this works on both.