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 → Create operation enables users to create new records in a specified table within a Ninox database. This is useful for automating data entry, integrating external sources (like web forms or other databases), and streamlining workflows that require adding information to Ninox tables.

Practical examples:

Automatically add new customer entries from a web form submission.
Sync data from another CRM or ERP system into Ninox.
Batch import records from CSV files or other sources.

Properties

Name	Type	Meaning
Team Name or ID	options	The ID of the team to access. Choose from the list, or specify an ID using an expression. Required to identify the correct workspace in Ninox.
Database Name or ID	options	The ID of the database to access. Choose from the list, or specify an ID using an expression. Only shown when a Team is selected. Required to target the correct database.
Table Name or ID	options	The ID of the table to access. Choose from the list, or specify an ID using an expression. Only shown when both Team and Database are selected. Required to specify where the record will be created.
Add All Fields	boolean	Whether to send all fields to Ninox or only specific ones. If enabled, all available fields will be included in the new record.
Fields	string[]	The names of fields for which data should be sent to Ninox. Only shown if "Add All Fields" is disabled. Allows specifying exactly which fields to populate in the new record.

Output

The output will contain the details of the newly created record(s) in Ninox.
The structure typically includes a json field with properties representing the created record's fields and their values as returned by the Ninox API.

Example output:

[
  {
    "json": {
      "id": 123,
      "field1": "value1",
      "field2": "value2",
      // ...other fields as defined in your Ninox table
    }
  }
]

No binary data is produced by this operation.

Dependencies

External Service: Requires access to a Ninox account and the relevant API credentials (ninoxApi).
n8n Configuration: The node must be configured with valid Ninox API credentials, which may include an API key or OAuth token depending on your Ninox setup.

Troubleshooting

Common issues:

Missing or incorrect IDs: Ensure that Team, Database, and Table IDs are correctly selected or entered. Invalid IDs will result in errors from the Ninox API.
Insufficient permissions: The provided Ninox API credentials must have permission to create records in the specified table.
Field mismatches: If you specify fields that do not exist in the target table, the API may return an error.
API limits: Ninox may enforce rate limits or payload size restrictions.

Common error messages:

"Invalid team/database/table ID": Double-check the selected or entered IDs.
"Authentication failed": Verify that your Ninox API credentials are correct and active.
"Field not found": Make sure all specified fields exist in the target table.