Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

Schema → Update

AI-generated

Overview

This node operation updates a record in a Ninox database schema. It is useful for scenarios where you need to modify existing data entries in Ninox tables programmatically, such as updating customer information, inventory details, or any other record-based data. The node supports updating specific fields or all fields of a record and can optionally perform an upsert operation to insert a new record if the specified record ID does not exist.

Use Case Examples

  1. Updating a customer record with new contact details.
  2. Modifying an inventory item's quantity and price.
  3. Upserting a record to ensure data consistency by creating it if it doesn't exist.

Properties

Name Meaning
Ninox Team The ID of the Ninox team to access, selectable from a list, URL, or direct ID input.
Ninox Database The ID of the Ninox database to access, selectable from a list, URL, or direct ID input.
Ninox Table The ID of the Ninox table to access, selectable from a list, URL, or direct ID input.
Record ID The ID of the record to update. This is required to specify which record to modify.
Upsert Boolean flag to insert a new record if the specified record ID does not exist, enabling update or create behavior.
Add All Fields Boolean flag to send all fields to Ninox or only specific ones when updating.
Fields List of specific field names to send data for when 'Add All Fields' is false.
Request Options Settings for batching, SSL certificate validation, proxy usage, and request timeout to control the HTTP request behavior.

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

  • Ninox API with authentication credentials

Troubleshooting

  • Ensure the Record ID is provided and valid; missing or incorrect IDs will cause update failures.
  • Verify Ninox Team, Database, and Table IDs are correct and accessible with the provided credentials.
  • If upsert is enabled, check that the API supports creating new records when the ID does not exist.
  • Network issues or incorrect proxy settings can cause request failures; verify connectivity and proxy configuration.
  • Timeouts may occur if the server is slow or unresponsive; adjust the timeout setting accordingly.

Links

Discussion