Actions10
Overview
The Upload File Attachment operation in the Ninox n8n node allows you to add a file as an attachment to a specific record within a table in your Ninox database. This is useful for automating workflows where files (such as images, PDFs, or documents) need to be programmatically attached to records—common scenarios include archiving invoices, storing signed contracts, or saving user-uploaded files directly into your Ninox system.
Practical examples:
- Automatically attach scanned receipts to expense records.
- Upload and link customer-signed agreements to their CRM entries.
- Store product images alongside inventory items.
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 the operation targets. |
| 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 select the correct table. |
| Record ID | string | The unique identifier of the record to which the file will be attached. Required to target the correct record. |
| Binary Property Name | string | The name of the binary property in the incoming item that contains the file data to upload. Default is data. Required to locate the file in the workflow input. |
| Attachment Field | string | (Optional) Name or ID of a specific field where the attachment should be added. If left empty, the file will be added to the record's default attachments area. |
Output
- The output is a JSON object with a success indicator:
{ "success": true } - No additional data about the uploaded file is returned.
- Binary Output: This operation does not return binary data; it only confirms success.
Dependencies
- External Service: Requires access to the Ninox API.
- Authentication: Needs valid Ninox API credentials configured in n8n (
ninoxApi). - n8n Configuration: The binary file to upload must be present in the specified binary property of the incoming item.
Troubleshooting
Common Issues:
- Missing or Incorrect IDs: If any of the required IDs (team, database, table, record) are missing or incorrect, the operation will fail.
- File Not Found: If the specified binary property does not exist or does not contain valid file data, the upload will not succeed.
- Permission Errors: Insufficient permissions on the Ninox account may prevent file uploads.
- API Key Issues: Invalid or expired API credentials will result in authentication errors.
Typical Error Messages & Resolutions:
"Record not found": Check that the Record ID, Table ID, Database ID, and Team ID are all correct and refer to existing entities."Binary property not found": Ensure the incoming item has the specified binary property containing the file."Unauthorized": Verify that the Ninox API credentials are correctly set up in n8n.