Actions30
- Schema Actions
- Record Actions
- File Actions
File → Delete
AI-generatedOverview
This node operation deletes a specific record from a Ninox database table. It is useful when you need to remove outdated or incorrect data entries from your Ninox database programmatically within an n8n workflow.
Use Case Examples
- Deleting a user record from a customer database table in Ninox when the user unsubscribes.
- Removing an obsolete inventory item record from a Ninox table to keep the database clean.
Properties
| Name | Meaning |
|---|---|
| Ninox Team | The ID of the Ninox team to access. It can be selected from a list, specified by URL, or directly by ID. |
| Ninox Database | The ID of the Ninox database to access. It can be selected from a list, specified by URL, or directly by ID. |
| Ninox Table | The ID of the Ninox table to access. It can be selected from a list, specified by URL, or directly by ID. |
| Record ID | The ID of the record to delete from the Ninox table. This is required to specify which record to remove. |
| Request Options | Additional options for the HTTP request such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
success- Indicates whether the record deletion was successful.deletedRecordId- The ID of the record that was deleted.
Dependencies
- Requires Ninox API access with appropriate credentials (API key or token).
Troubleshooting
- Ensure the provided Team ID, Database ID, Table ID, and Record ID are correct and exist in Ninox.
- Check API credentials and permissions to confirm the node has rights to delete records.
- If SSL errors occur, consider enabling the 'Ignore SSL Issues' option or verify the SSL certificate.
- Timeouts can happen if the Ninox API is slow; adjust the timeout setting accordingly.
Links
- Ninox REST API Documentation - Official Ninox API documentation for reference on endpoints and data structure.
- Ninox n8n Node GitHub Repository - Source code and additional information about the Ninox node for n8n.