Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

File → Update

AI-generated

Overview

This node operation updates a record in a Ninox database table. It is useful for scenarios where you need to modify existing data entries in Ninox, such as updating customer information, inventory details, or any other record stored in Ninox tables. The node supports specifying the team, database, and table where the record resides, and allows updating specific fields or all fields of the record. It also supports an upsert option to create a new record if the specified record ID does not exist.

Use Case Examples

  1. Updating a customer record in a Ninox database by specifying the record ID and the fields to update.
  2. Modifying inventory data in a Ninox table by selecting the appropriate team, database, and table, then providing the updated field values.
  3. Using the upsert option to either update an existing record or create a new one if the record ID is not found.

Properties

Name Meaning
Ninox Team The ID of the Ninox team to access. Can be selected from a list, specified by URL, or directly by ID.
Ninox Database The ID of the Ninox database to access within the selected team. Can be selected from a list, specified by URL, or directly by ID.
Ninox Table The ID of the Ninox table to access within the selected database. Can be selected from a list, specified by URL, or directly by ID.
Record ID The ID of the record to update in the Ninox table. This is required to identify which record to modify.
Upsert A boolean option to insert a new record if the specified record ID does not exist. When enabled, the operation will update existing records or create new ones.
Add All Fields Whether to send all fields to Ninox or only specific ones when updating the record.
Fields The names of specific fields to send to Ninox for updating, used only if 'Add All Fields' is false.
Request Options Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration.

Output

JSON

  • recordId - The ID of the updated record in Ninox.
  • success - Indicates whether the update operation was successful.
  • data - The updated record data returned from Ninox.

Dependencies

  • An API key credential for Ninox API authentication

Troubleshooting

  • Ensure the provided Team ID, Database ID, Table ID, and Record ID are correct and exist in Ninox to avoid errors.
  • If the 'Upsert' option is enabled, verify that the API permissions allow record creation.
  • Check network connectivity and proxy settings if requests fail or time out.
  • If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option cautiously.

Links

Discussion