Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

File → Create

AI-generated

Overview

This node operation allows users to create a new file record in Ninox, a cloud-based database platform. It is useful for automating the process of adding files to a specific Ninox team, database, and table. For example, a user can automate uploading documents or images related to projects or clients directly into Ninox from other systems or workflows.

Use Case Examples

  1. Automate uploading project documents to a Ninox database table.
  2. Create new file entries in Ninox for client records from an external form submission.

Properties

Name Meaning
Ninox Team The ID of the Ninox team to access. Users can select from a list, provide a URL, or enter the team ID directly.
Ninox Database The ID of the Ninox database to access within the selected team. Can be selected from a list, specified by URL, or entered manually.
Ninox Table The ID of the Ninox table where the file record will be created. Can be selected from a list, specified by URL, or entered manually.
Add All Fields Boolean option to send all fields to Ninox or only specific ones when creating the file record.
Fields The names of specific fields to send to Ninox if 'Add All Fields' is false. Multiple fields can be specified.
Request Options Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings.

Output

JSON

  • id - The unique identifier of the created file record in Ninox.
  • fields - The data fields of the created file record as stored in Ninox.
  • createdAt - Timestamp when the file record was created.

Dependencies

  • Requires Ninox API credentials for authentication.

Troubleshooting

  • Ensure the Ninox Team, Database, and Table IDs are correctly specified and accessible with the provided credentials.
  • If the node fails due to SSL issues, consider enabling the 'Ignore SSL Issues' option in Request Options.
  • Batching settings should be configured properly to avoid rate limiting or timeouts.
  • Common errors include invalid resource IDs or insufficient permissions, which can be resolved by verifying credentials and resource access rights.

Links

Discussion