Let an agent read your table
Give it access to the space where the database lives, and the agent answers with that data.
An agent can answer with the data in your databases. But the table existing isn't enough: you have to give it access.
The table has to live in a space
This is the part that gets missed. A page saved under Private is invisible to the agent, and the app doesn't warn you: the agent simply replies that it doesn't have access.
Create the space first, and the page with the database inside it. If the page already exists somewhere else, moving it into the space works too — it takes its child pages along.
Granting access
On the agent, Knowledge & tools → Add space. Pick the space, and from then on the agent can see the tables it contains.
Access is granted per space, not per table. It's the same decision you already made when you set up the team's permissions, which is why it's managed in one place.
Asking it
From the chat, the agent can now answer about those rows: how many orders are in production, which one is the largest, which ones are pending.
There's no sync to wait for: linking the space makes the tables available right then.