Actions10
Overview
The Download Attached File operation for the "Default" resource in the Ninox n8n node allows you to download a specific file attachment from a record in a Ninox database table. This is useful when you need to retrieve files (such as images, documents, or other attachments) that have been uploaded to records in your Ninox database.
Common scenarios:
- Automating the backup of attached files from Ninox records.
- Processing or analyzing files stored in Ninox via downstream n8n nodes.
- Integrating Ninox with external storage or document management systems.
Practical example:
You might use this operation to automatically download invoices attached to customer records and then forward them to an accounting system or archive them in cloud storage.
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 Ninox workspace. |
| Database Name or ID | options | The ID of the database to access. Choose from the list, or specify an ID using an expression. Required to select the target database within the team. |
| Table Name or ID | options | The ID of the table to access. Choose from the list, or specify an ID using an expression. Required to select the table containing the record with the attachment. |
| Record ID | string | ID of the record with the attachments. Specifies which record's file should be downloaded. |
| File Name | string | The file ID (name) of the attachment to download from the specified record. |
Output
Binary Data:
The output will contain the downloaded file as binary data. The binary property will include the file content, filename, MIME type, and size. This allows you to pass the file to subsequent nodes for further processing, saving, or transformation.JSON Structure:
The JSON output will typically reference the binary property name and may include metadata about the file. For example:
{
"binary": {
"data": {
"data": "<base64-encoded file>",
"fileName": "example.pdf",
"mimeType": "application/pdf"
}
}
}
(The actual property name may vary depending on configuration.)
Dependencies
- External Service: Requires access to the Ninox API.
- API Key/Credentials: You must configure valid Ninox API credentials (
ninoxApi) in n8n. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid IDs: If the Team, Database, Table, Record, or File Name is incorrect or missing, the node will fail to find the file and may return a "Not Found" error.
- Missing Credentials: If Ninox API credentials are not set up or are invalid, authentication errors will occur.
- Permission Denied: The user associated with the API key may lack permission to access the specified resource or file.
- File Not Attached: If the specified file does not exist on the record, an error will be thrown.
Error messages and resolutions:
"404 Not Found": Check that all IDs (team, database, table, record, file) are correct and that the file exists."401 Unauthorized": Ensure your Ninox API credentials are correctly configured in n8n."403 Forbidden": Verify that your Ninox user has sufficient permissions to access the requested file.