Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs.
Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs. On Nagent, Ninox is exposed as a fully-configurable databases integration that any agent can call — 4 actions, and API key authentication. No code is required to wire Ninox into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ninox to automate the kinds of tasks databases teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Ninox into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Ninox, with input parameters and output schema. Drop these into any step of an agent built in Helix.
NINOX_DELETE_RECORDTool to delete a record from a specified table. Use after confirming workspace, database, table, and record IDs.
Input parameters
Workspace (team) identifier. Obtain from GET /teams endpoint.
Table identifier. Ninox tables are identified by letters starting with A, B, C, etc. Obtain from GET /teams/{team_id}/databases/{database_id}/tables endpoint.
Record identifier to delete. Typically numeric. Obtain from GET /teams/{team_id}/databases/{database_id}/tables/{table_id}/records endpoint.
Database identifier. Obtain from GET /teams/{team_id}/databases endpoint.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NINOX_GET_DATABASESRetrieves all databases within a specific Ninox team. This action lists all databases (workspaces) that belong to a given team in Ninox. Each database contains tables, fields, and records for organizing data. Use this action when you need to: - List all available databases in a team - Find a specific database by name - Get database IDs for further operations Note: You must have a valid team_id. Use the GET /teams endpoint to retrieve team IDs first.
Input parameters
The unique identifier of the Ninox team to list databases for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NINOX_GET_TEAMRetrieves data from a single team (workspace) by its ID. Use when you need to get workspace details including the workspace ID and name.
Input parameters
The unique identifier of the Ninox team/workspace to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NINOX_LIST_TEAMSRetrieves all workspaces (teams) accessible to the authenticated user. This action lists all Ninox teams (workspaces) that the user has access to. Each team contains databases, which in turn contain tables and records. Use this action when you need to: - List all available workspaces - Find a specific workspace by name - Get workspace IDs for further operations (databases, tables, records) Note: The team_id from this response is required for most other Ninox API operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 86 agents privately built on Nagent that already use Ninox.
Build on Nagent
Connect Ninox to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Ninox, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ninox is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ninox is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ninox steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Ninox event fires, the agent kicks off automatically.
Every Ninox action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Ninox ships with 4 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ninox together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ninox-based workflows tailored to your business.