# Ninox AI integration on Definable

> Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs.

## What this connects

Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs.

Vendor: https://ninox.com/

## Tools available

**4** tools available. First 4:

- `NINOX_DELETE_RECORD` — Delete Record — Tool to delete a record from a specified table. Use after confirming workspace, database, table, and record IDs.
- `NINOX_GET_DATABASES` — Get Databases — Retrieves 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.
- `NINOX_GET_TEAM` — Get Team — Retrieves data from a single team (workspace) by its ID. Use when you need to get workspace details including the workspace ID and name.
- `NINOX_LIST_TEAMS` — List Teams — Retrieves 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.

## Auth

Auth schemes: `API_KEY`.

## How agents use Ninox

Inside a Definable workflow, Ninox is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Ninox** — the Researcher (GPT-5.5) pulls context from Ninox (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Ninox** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Ninox (create record, post message, draft email).
- **Designer / Engineer → Distributor → Ninox** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Ninox (attach file, open PR comment, post status).

The Verifier checks every Ninox call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- databases — https://definable.ai/apps/category/databases/
- app builder — https://definable.ai/apps/category/app-builder/

## Related

- HTML page: https://definable.ai/apps/ninox/
- Same category (databases): https://definable.ai/apps/category/databases/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt