Ninox

Read, create and update data from Ninox

Actions10

Overview

The "List Attached Files" operation of the Ninox n8n node retrieves all files attached to a specific record within a table in your Ninox database. This is useful for automating workflows that need to process, audit, or transfer attachments stored in Ninox records.

Common scenarios:

Listing all documents or images attached to a customer or project record.
Auditing which files are associated with a particular entry before performing further actions (e.g., download, backup, or delete).
Integrating Ninox attachments with other systems (e.g., copying files to cloud storage).

Practical example:
You have a CRM built in Ninox and want to automatically list all files attached to a contact's record whenever a new support ticket is created, so you can review relevant documents.

Properties

Name	Type	Meaning
Team Name or ID	options	The ID of the team to access. Choose from a list or specify an ID using an expression. Required to identify the correct workspace in Ninox.
Database Name or ID	options	The ID of the database to access. Choose from a list or specify an ID using an expression. Required to select the right database within the team.
Table Name or ID	options	The ID of the table to access. Choose from a list or specify an ID using an expression. Required to target the correct table within the database.
Record ID	string	The ID of the record whose attachments you want to list. Required to specify which record’s files should be retrieved.

Output

The output will be a JSON array where each item represents an attached file for the specified record. Each object typically contains:

id: Unique identifier of the file.
name: File name.
size: File size in bytes.
createdAt: Timestamp when the file was uploaded.
contentType: MIME type of the file.
Other metadata as provided by Ninox.

Example output:

[
  {
    "id": "file_12345",
    "name": "invoice.pdf",
    "size": 23456,
    "createdAt": "2024-06-01T12:34:56Z",
    "contentType": "application/pdf"
  },
  {
    "id": "image_67890",
    "name": "photo.jpg",
    "size": 54321,
    "createdAt": "2024-06-02T09:10:11Z",
    "contentType": "image/jpeg"
  }
]

Dependencies

Ninox API: Requires a Ninox account and access to the relevant team/database/table/record.
API Credentials: You must configure the ninoxApi credential in n8n with appropriate API key/token.
n8n Configuration: No special environment variables required unless using a custom Ninox API base URL.

Troubleshooting

Common issues:

Invalid IDs: If any of the Team, Database, Table, or Record IDs are incorrect or missing, the node will fail with a "Not Found" or similar error.
Insufficient permissions: If the API credentials do not have access to the specified resources, you may receive a "403 Forbidden" or "401 Unauthorized" error.
No attachments: If the record has no attached files, the output will be an empty array.

Error messages and resolutions:

"Record not found": Double-check the Record ID and ensure it exists in the specified table.
"Team/Database/Table not found": Verify that the selected IDs are correct and accessible with your credentials.
"Authentication failed": Ensure your Ninox API credentials are valid and have sufficient permissions.