Actions30
- Schema Actions
- Record Actions
- File Actions
Schema → Upload File Attachment
AI-generatedOverview
This node operation uploads a file attachment to a specified record in a Ninox database schema. It is useful for automating the process of adding files to records within Ninox, such as attaching documents, images, or other media to database entries. For example, it can be used to upload invoices, contracts, or photos directly to a record in Ninox from an external source or workflow.
Use Case Examples
- Uploading a PDF invoice to a customer record in Ninox.
- Adding a photo attachment to a product record automatically after image processing.
Properties
| Name | Meaning |
|---|---|
| Ninox Team | The ID of the Ninox team to access. This can be selected from a list, specified by URL, or entered as an ID. |
| Ninox Database | The ID of the Ninox database to access. This can be selected from a list, specified by URL, or entered as an ID. |
| Ninox Table | The ID of the Ninox table to access. This can be selected from a list, specified by URL, or entered as an ID. |
| Record ID | The ID of the record within the Ninox table where the file attachment will be uploaded. |
| Binary Property Name | The name of the binary property in the input data where the file to upload is found. |
| Attachment Field | The name or ID of the field in the Ninox record where the attachment should be added. If left empty, the file will be added to the record's default attachment field. |
Output
JSON
id- The ID of the record to which the file was attached.attachmentField- The field in the record where the file was uploaded.fileName- The name of the uploaded file.fileSize- The size of the uploaded file in bytes.fileType- The MIME type of the uploaded file.
Dependencies
- Requires Ninox API credentials for authentication.
Troubleshooting
- Ensure the Ninox Team, Database, and Table IDs are correct and accessible with the provided credentials.
- Verify the binary property name matches the input data containing the file to upload.
- Check that the record ID exists in the specified table.
- If the attachment field is specified, ensure it exists and is configured to accept file attachments.
- Network or API errors may occur if the Ninox API base URL or credentials are incorrect or expired.
Links
- Ninox REST API Documentation - Official Ninox API documentation for reference on endpoints and data formats.
- Ninox n8n Node GitHub Repository - Source code and additional information about the Ninox node for n8n.