Can Lyro read a KPI value or a dashboard out of Databox?

No. Every action in this toolkit sits on the ingestion side: List Accounts, Create Data Source, Create Dataset, Push Data to Dataset, Get Dataset Ingestion Status, Delete Dataset, and Delete Data Source. Lyro feeds the dashboards and verifies the feed arrived; reading a metric back is still done in Databox.

What does Lyro need before it can create a dataset?

A data source to put it in. Create Data Source takes an account ID, a title, and a timezone, and the account ID comes from List Accounts. Create Dataset then needs a title, that data source ID, and the primary keys Databox uses to tell one record from another.

Is deleting a Databox dataset reversible?

No. Delete Dataset is permanent, and Delete Data Source is worse: it removes every dataset associated with that source as well. Because neither can be undone, deletions are worth treating as a request a person confirms rather than something to run on a loose instruction.

How does Lyro know a data push succeeded?

The push returns an ingestion ID, and Get Dataset Ingestion Status takes that ID together with the dataset ID to report whether the ingestion completed. Lyro runs the two as a pair, so the answer to whether the numbers are current is checked rather than assumed.

Databox MCP integration

Creates Databox data sources and datasets, pushes records into them, verifies each ingestion landed, and removes what is no longer feeding a dashboard.

Connect Databox See all integrations

7actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Push data to dataset (v1)
Lyro sends data points to a Databox dataset for visualization and tracking. Your team logs metrics and KPIs into dashboards without manual entry.
Create data source
Lyro sets up a new data source in Databox during a conversation. Your team can instantly create analytics pipelines without leaving chat.
Get dataset ingestion status
Lyro checks the status of a specific data ingestion to a dataset. Your team monitors pipeline health and debugs failed data loads.

See all 7 actions

How businesses use Databox + Lyro

Each card is one request a support team gets, and the Databox actions Lyro runs to close it.

Set up a data source and its first dataset
Lyro finds the account ID, creates the data source with its title and timezone, then creates a dataset inside it with the primary keys that identify a unique record.
List AccountsCreate Data SourceCreate Dataset
Push a batch of records into a dataset
Lyro sends an array of records matching the dataset schema into the dataset by ID, so a number that changed in a source system reaches the dashboard reading from it.
Push Data To DatasetCreate DatasetList Accounts
Confirm an ingestion actually landed
Lyro takes the ingestion ID returned by the push and checks its status against the dataset, so a silent failure is caught rather than showing up as a dashboard that quietly stopped moving.
Get Dataset Ingestion StatusPush Data To DatasetList Accounts
Retire datasets and sources that are finished
Lyro removes a dataset that no longer feeds anything, or the whole data source when a tool is decommissioned, keeping the account free of feeds nobody reads.
Delete DatasetDelete Data SourceList Accounts

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Databox actions it has and picks the ones a request needs.

01
Connect Databox
Authorize the Databox account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Databox actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Databox · Lyro

Everything else about Databox

Setup, permissions, and the limits of what Lyro can do inside Databox.

No. Every action in this toolkit sits on the ingestion side: List Accounts, Create Data Source, Create Dataset, Push Data to Dataset, Get Dataset Ingestion Status, Delete Dataset, and Delete Data Source. Lyro feeds the dashboards and verifies the feed arrived; reading a metric back is still done in Databox.

Every action available in Databox

All 7 actions your agent can call on Databox, straight from the live MCP connection.

Create dataset
Create a new dataset in Databox data source.
Create data source
Create a new data source in Databox.
Delete dataset
Delete a dataset by ID in Databox.
Delete data source
Delete a data source by ID in Databox.
Get dataset ingestion status
Check the status of a specific data ingestion for a dataset.
List accounts
Retrieve all Databox accounts accessible to the authenticated user.
Push data to dataset (v1)
Push data points to a Databox dataset using the v1 API.