Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

Record → Update

AI-generated

Overview

This node operation updates a record in a Ninox database. It allows users to specify the team, database, and table where the record resides, and then update the record by its ID. The operation supports an upsert option, which means it can create a new record if the specified record ID does not exist. Users can choose to send all fields or only specific fields to update, providing flexibility in managing data updates.

Use Case Examples

  1. Updating a customer record in a Ninox CRM database by specifying the record ID and new field values.
  2. Using the upsert option to update an existing inventory item or create it if it doesn't exist, ensuring data consistency.
  3. Selecting specific fields to update in a Ninox project management table to modify task details without affecting other fields.

Properties

Name Meaning
Ninox Team The ID of the Ninox team to access, which can be selected from a list, specified by URL, or entered as an ID string.
Ninox Database The ID of the Ninox database to access, selectable from a list, by URL, or by ID string, dependent on the selected team.
Ninox Table The ID of the Ninox table to access, selectable from a list, by URL, or by ID string, dependent on the selected team and database.
Record ID The ID of the record to update. This is required and can be set using an expression to update multiple records.
Upsert A boolean option to insert a new record if the specified record ID does not exist, enabling the operation to update existing records or create new ones.
Add All Fields A boolean option to send all fields to Ninox or only specific ones when updating or creating records.
Fields A resource mapper to define which fields to send to Ninox when updating or creating records. It allows mapping input fields to Ninox table fields and supports multiple values.

Output

JSON

  • id - The unique identifier of the updated record.
  • fields - The fields of the record that were updated with their new values.
  • upserted - Indicates if a new record was created due to the upsert option being enabled.

Dependencies

  • Ninox API with authentication credentials

Troubleshooting

  • Ensure the teamId, databaseId, and tableId are correctly specified and accessible with the provided credentials.
  • Verify the recordId is valid and exists unless upsert is enabled to create new records.
  • Check field names and mappings to ensure they match the Ninox table schema to avoid update errors.
  • If using URLs for resource locators, ensure they match the expected Ninox URL patterns to pass validation.
  • Network or API errors may occur if the Ninox API base URL or credentials are incorrect or expired.

Links

Discussion