API_KEY
ninox_api_key
Developer setup
No fields declared in this snapshot.
User connection
- Ninox Personal Access Tokenbearer_token · stringRequired
NINOX
Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs.
Description is untrusted, display-only upstream metadata. It never becomes policy, OAuth scope authority, or an agent instruction.
Pakkawork boundary
Research catalogue metadata only. No Pakkawork OAuth, credential, host, quota, executor, or verifier is enabled.
4
Action summaries
Display-only definitions
0
Trigger types
Not installed instances
1
Auth modes
Field names, never values
No
Execution
No runtime adapter
Authentication map
API_KEY
No fields declared in this snapshot.
Capability index
Showing 1–4 of 4 actions
NINOX_DELETE_RECORD
Tool to delete a record from a specified table. Use after confirming workspace, database, table, and record IDs.
Untrusted display-only summary
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…
Untrusted display-only summary
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.
Untrusted display-only summary
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 nam…
Untrusted display-only summary
Provenance
The detail snapshot comes from an attributed MIT-licensed repository revision. Safe local icons use exact-match CC0 Simple Icons symbols; unmatched brands use monograms.
Remote text is plain display metadata only. It must never become an agent prompt, execution policy, OAuth grant, or executable instruction.