Ninox

Read, create and update data from Ninox

Actions10

Overview

The Ninox node for n8n allows you to interact with the Ninox database platform. Specifically, the Default resource with the Read operation retrieves a single record from a specified table in your Ninox database by its Record ID. This is useful when you need to fetch detailed information about a specific entry, such as a customer, order, or any other entity stored in Ninox.

Common scenarios:

Fetching a user's profile details by their unique ID.
Retrieving an order's full data for further processing or integration.
Looking up a specific record to enrich or validate data in an automation workflow.

Practical example:
You have a workflow that receives a user ID and needs to pull all related information from your Ninox "Users" table to send a personalized email.

Properties

Name	Type	Meaning
Team Name or ID	options	The ID of the team to access. Choose from a list or specify via expression. Required to identify which Ninox team (workspace) contains your data.
Database Name or ID	options	The ID of the database within the selected team. Choose from a list or specify via expression. Required to select the correct database.
Table Name or ID	options	The ID of the table within the selected database. Choose from a list or specify via expression. Required to target the correct table for the record lookup.
Record ID	string	The unique identifier of the record to return. Required to specify exactly which record should be fetched from the table.

Output

The output will be a json object containing all fields of the requested record.
The structure of the output depends on your Ninox table schema, but typically includes:
- All field names and values for the record.
- System fields such as id, createdAt, updatedAt, etc.

Example output:

{
  "id": "12345",
  "Name": "John Doe",
  "Email": "john@example.com",
  "Status": "Active",
  "createdAt": "2023-01-01T12:00:00Z",
  "updatedAt": "2023-02-01T15:30:00Z"
}

No binary data is returned by this operation.

Dependencies

External Service: Requires access to a Ninox account and the relevant API credentials.
n8n Credentials: You must configure the ninoxApi credential in n8n with your Ninox API key.
Environment Variables: None required by default.

Troubleshooting

Common issues:

Invalid or missing credentials: Ensure your ninoxApi credentials are correctly set up in n8n.
Incorrect IDs: If you provide an invalid Team, Database, Table, or Record ID, the node will fail to find the record.
Permissions: Your Ninox API user must have permission to read records in the specified table.

Common error messages:

"Record not found": The provided Record ID does not exist in the specified table. Double-check the ID.
"Unauthorized": The API credentials are incorrect or lack sufficient permissions.
"Team/Database/Table not found": One of the parent resources (team, database, or table) was not found. Verify all IDs.

How to resolve:

Use the dropdowns in the node properties to select valid teams, databases, and tables.
Check your Ninox API key and permissions.
Confirm the Record ID exists in the targeted table.