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 → List operation retrieves records from a specified table within a Ninox team and database. This is useful for automating data extraction, reporting, or integrating Ninox data with other systems.

Common scenarios:

Fetching all or filtered records from a Ninox table for further processing.
Synchronizing Ninox data with external tools (e.g., CRMs, spreadsheets).
Building dashboards or reports based on live Ninox data.

Example use cases:

Retrieve all customer records from a "Customers" table for email marketing.
Get only recently updated entries for incremental synchronization.
Filter records by specific field values (e.g., status = "Active").

Properties

Name	Type	Meaning
Team Name or ID	options	The ID of the Ninox team to access. Select from a list or specify via expression.
Database Name or ID	options	The ID of the database within the selected team. Select from a list or specify via expression.
Table Name or ID	options	The ID of the table within the selected database. Select from a list or specify via expression.
Return All	boolean	Whether to return all results (true) or limit the number of returned records (false).
Page	number	The page of results to return (used when "Return All" is false).
Limit	number	Maximum number of results to return per page (when "Return All" is false). Range: 1–250.
Additional Options	collection	Extra options to refine which records are returned. See below for details.

Additional Options (collection):

Sort by Field: Define sorting rules by specifying one or more fields and sort directions (ascending/descending).
Sort by Latest Modified: Show last changed records first (not combinable with "Sort by Field").
Sort by Latest Created: Show newest records first (not combinable with "Sort by Field").
Filters: JSON string to filter records by field values (e.g., {"fields": {"Email": "example@mail.com"}}).
Since ID: Only show records with an ID greater than the given value.
Since Sequence: Only show records created or modified since this sync sequence number.

Output

The output is a list (array) of Ninox records in the json field.
Each record typically contains key-value pairs representing the fields and their values from the Ninox table.
The structure of each record depends on your Ninox table schema and any filters applied.

Example output:

[
  {
    "id": 123,
    "Name": "John Doe",
    "Email": "john@example.com",
    "Status": "Active",
    ...
  },
  {
    "id": 124,
    "Name": "Jane Smith",
    "Email": "jane@example.com",
    "Status": "Inactive",
    ...
  }
]

No binary data is produced by this operation.

Dependencies

External Service: Requires access to a Ninox account and its API.
API Key/Credentials: You must configure the ninoxApi credential in n8n with appropriate permissions.
n8n Configuration: Ensure the Ninox node is installed and credentials are set up in your n8n instance.

Troubleshooting

Common issues:

Missing or invalid credentials: Ensure your Ninox API credentials are correctly configured in n8n.
Incorrect IDs: Double-check that the Team, Database, and Table IDs are correct and accessible with your credentials.
Pagination confusion: If "Return All" is false, make sure to set "Page" and "Limit" appropriately to retrieve the desired records.
Filter syntax errors: When using the "Filters" option, ensure the JSON is valid and matches your Ninox field names.

Possible error messages:

"401 Unauthorized": Check your Ninox API credentials.
"404 Not Found": One of the provided IDs (team, database, table) does not exist or is inaccessible.
"400 Bad Request": Likely due to malformed filters or parameters; review your input values.