Find the right DataLens dashboard and dataset from chat
Connect Yandex DataLens to the AI agent: collections, workbooks, dashboards, datasets and connections. The agent locates a report and shows what already exists.
How the agent works with Яндекс DataLens
The agent calls api.datalens.tech and walks the account through RPC endpoints: it lists the directory of collections and workbooks page by page, descends into them and collects dashboards, charts, datasets and source connections. It then maps out how the objects relate — which chart sits on which dataset, which dataset on which connection — spots duplicates of the same report and points you to the one you need.
The agent understands the main thing about DataLens up front: the API returns how a report is built, not what is inside it. A dashboard comes back as configuration, a dataset as fields, sources and settings, but there are no data rows in the response. So when asked about numbers the agent does not retell the dashboard from memory — it goes to the source system for them and says that DataLens itself does not hand out figures over the API.
There are exactly two changing operations here — exporting a workbook and importing it into a collection — and both run in two beats: the agent starts the task, waits for the file to be ready and only then moves it into another collection in the same organization. It does not edit or delete dashboards, charts or datasets. Everything else is reading: report inventory, object permissions, checking what a specific user can reach and change history from any date you name.
The connection is a sign-in to a Yandex account with a code: no tokens to copy, and the access lifetime is renewed automatically. The walk through the account is paginated, so on a large organization the agent takes the directory in parts and builds up the object links as it descends rather than in one call. It holds the request rate within the limit and names an empty result plainly, telling «no reports» apart from «reports not visible» instead of passing one off as the other.
Integration scenarios
Navigating collections and workbooks
The agent walks through your organization's collections and workbooks and points you to the dashboard, dataset or source connection you need.
Report inventory
The agent lists dashboards, charts and datasets, spots duplicates of the same report and shows how the objects relate to each other.
Access and change audit
The agent shows permissions on objects, checks what a specific user can reach and pulls change history from any date you name.
Moving a workbook between collections
The agent exports a workbook, waits for the file to be ready and imports it into another collection in the same organization.
Licenses and embed links
The agent pulls the organization licenses and the embed links of objects and shows which reports are exposed outside and what the current plan still covers.
What a dataset is built from
The agent opens up the dataset fields, sources and settings so you can see which breakdowns exist at all — for the numbers themselves it goes to the source system.
Яндекс DataLens examples
В коллекции «Финансы», воркбук «Отчётность 2026» — и у него есть близнец.
Обошёл 6 коллекций и 23 воркбука: второй такой же дашборд лежит в «Архиве» и тянет тот же датасет. Доступ к обоим только у пяти человек из отдела.
How to connect
Before you connect
- A Yandex account that belongs to the right organization.
- Organization admin rights for whoever grants the access.
- 1
Sign in at datalens.ru with your account
Open datalens.ru and sign in with the Yandex account you use for dashboards. Pick the organization at the top: roles are granted on it.
- 2
Check that a DataLens instance exists
If the organization opens without DataLens, an administrator creates it: datalens.ru/promo → “Get started in the cloud”. A regular member cannot activate it.
- 3
In Users invite the account with a role
In “Service settings” → “Users” invite the account with “Send invitation” and assign a role: datalens.metaReader for reading, datalens.admin for full access.
- 4
Assign the viewer role on collections
An organization role alone does not expose content: assign datalens.collections.viewer and datalens.workbooks.viewer on each collection and workbook.
FAQ
By signing in to your Yandex account with a code — no tokens to copy. DataLens grants permissions at the organization level, so the account needs a role there, plus viewer access on collections and workbooks, otherwise their contents stay invisible.
The structure of your account: collections, workbooks, dashboards, charts, datasets and connections, how they relate, their permissions, change history, organization licenses and embed links.
No. The API returns dashboard configuration and dataset structure — fields, sources, settings — but not data rows. For the numbers themselves the agent goes to the source system, not to DataLens.
Almost never: it reads objects, and the only changing operations available to it are exporting a workbook and importing it into a collection. It does not edit dashboards, charts or datasets.