Why does Lyro look up a team before it can read a database?

Get Databases requires a team ID, and most other Ninox operations do too. List Teams returns the IDs for every workspace the authenticated account can see, so Lyro resolves the team first and then reads its databases.

Can Lyro create or update Ninox records?

No. Delete Record is the only record-level write in this toolkit; Get Databases, Get Team and List Teams are reads. Creating rows or editing field values needs a different route into Ninox.

Is a record Lyro deletes recoverable?

Not through this integration - there is no restore or undo action in the toolkit. Because of that, Lyro confirms the workspace, database, table and record IDs before calling Delete Record, and hands the request to a human agent with the full conversation history when any of them is ambiguous.

Which Ninox workspaces can Lyro reach?

Exactly the ones the connected credentials can. List Teams returns only the workspaces accessible to the authenticated user, so scoping is controlled by which Ninox account you connect rather than configured separately in Lyro.

Ninox MCP integration

Lists accessible Ninox workspaces, returns the databases inside a team, and deletes a record once its workspace, database and table IDs check out.

Connect Ninox See all integrations

4actions available

Three actions you can hand over today

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

Get databases
Lyro lists all tables and databases in a Ninox workspace so you find the right data source for a query. This navigates large workspaces without getting lost.
List teams
Lyro shows all Ninox workspaces you have access to so you can switch between projects or invite collaborators. This simplifies team and data management.
Delete record
Lyro removes a single record from a Ninox table to clean up duplicate or outdated entries. This keeps your database accurate and organized.

See all 4 actions

How businesses use Ninox + Lyro

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

Map the workspaces and databases in an account
Lyro lists the Ninox teams the connected account can reach and then returns the databases inside the one being asked about, so a team ID never has to be looked up by hand.
List TeamsGet Databases
Remove a record once its IDs are verified
Lyro confirms the workspace by ID before deleting a record from a table, so the destructive call only runs against a target that has been checked.
Get TeamDelete Record

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 Ninox actions it has and picks the ones a request needs.

01
Connect Ninox
Authorize the Ninox 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 Ninox 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

Ninox · Lyro

Everything else about Ninox

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

Get Databases requires a team ID, and most other Ninox operations do too. List Teams returns the IDs for every workspace the authenticated account can see, so Lyro resolves the team first and then reads its databases.

Every action available in Ninox

All 4 actions your agent can call on Ninox, straight from the live MCP connection.

Delete record
Delete a record from a specified table.
Get databases
Retrieves all databases within a specific Ninox team.
Get team
Retrieves data from a single team (workspace) by its ID.
List teams
Retrieves all workspaces (teams) accessible to the authenticated user.