# Ninox

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

- **Category:** databases
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 4
- **Triggers:** 0
- **Slug:** `NINOX`
- **Version:** 20260227_00

## Tools

### Delete Record

**Slug:** `NINOX_DELETE_RECORD`

Tool to delete a record from a specified table. Use after confirming workspace, database, table, and record IDs.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | Yes | Workspace (team) identifier. Obtain from GET /teams endpoint. |
| `table_id` | string | Yes | 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_id` | string | Yes | Record identifier to delete. Typically numeric. Obtain from GET /teams/{team_id}/databases/{database_id}/tables/{table_id}/records endpoint. |
| `database_id` | string | Yes | Database identifier. Obtain from GET /teams/{team_id}/databases endpoint. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Databases

**Slug:** `NINOX_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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | Yes | The unique identifier of the Ninox team to list databases for. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Team

**Slug:** `NINOX_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.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `team_id` | string | Yes | The unique identifier of the Ninox team/workspace to retrieve. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Teams

**Slug:** `NINOX_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.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |