Actions10
Overview
The Ninox node for n8n allows you to interact with your Ninox databases. It supports reading, creating, updating, and deleting records, as well as managing file attachments and running custom Ninox scripts. This node is useful for automating workflows that require integration with Ninox, such as syncing data between Ninox and other systems, processing records in bulk, or handling file attachments programmatically.
Practical examples:
- Syncing new contacts from a Ninox table to a CRM.
- Automatically uploading files to Ninox records when they are received via email.
- Running custom queries on your Ninox database and using the results in downstream workflow steps.
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 for all operations. |
| Database Name or ID | options | The ID of the database to access. Choose from the list, or specify an ID using an expression. Required for all operations. |
| Table Name or ID | options | The ID of the table to access. Choose from the list, or specify an ID using an expression. Required for most operations except "Ninox Script". |
Output
- The output will be a JSON object (or array of objects) representing the data returned by the Ninox API for the selected operation.
- For operations involving file downloads ("Download Attached File"), the node can output binary data representing the file content.
- For create, update, delete, upload, and delete file operations, the output may include a simple success confirmation:
{ "success": true } - For list/read/query operations, the output will contain the fields and values of the Ninox records retrieved.
Dependencies
- External Service: Requires access to the Ninox API.
- API Key/Credentials: You must configure Ninox API credentials in n8n under the name
ninoxApi. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Credentials: If your Ninox API credentials are incorrect or missing, requests will fail with authentication errors.
- Missing Required Fields: If you do not provide required properties (e.g., Team, Database, or Table IDs), the node will throw validation errors.
- Incorrect IDs: Supplying invalid team, database, or table IDs will result in "not found" or similar errors from the Ninox API.
- File Upload/Download Errors: If the specified file or record does not exist, or if the binary property name is incorrect, file operations may fail.
Error Messages and Resolutions:
"401 Unauthorized": Check your Ninox API credentials in n8n."404 Not Found": Verify that the provided Team, Database, Table, Record, or File IDs are correct and exist in Ninox."Missing required parameter": Ensure all required input properties are filled in the node configuration.