Nexoid icon

Nexoid

Connect N8N to Nexoid via the Nexoid API. You will need an API service account which you can make inside the Nexoid Web Application (https://app.nexoid.com)
Join our community

Actions5

Overview

This node connects to the Nexoid API to update an existing record in a specified Nexoid record type (similar to a table in a database). It authenticates with the Nexoid API using stored credentials, manages session tokens, and sends a PATCH request to update the record data. This is useful for workflows that need to modify existing data entries in Nexoid, such as updating contact information or invoice details.

Use Case Examples

  1. Updating a contact record with new phone number and email address.
  2. Modifying an invoice record to change the payment status or amount.

Properties

Name Meaning
Record type The type of record to update, analogous to a table name in a database (e.g., 'contact' or 'invoice'). This determines which Nexoid object is being updated.
Record ID The unique identifier of the record to update. The node automatically strips any prefix (e.g., 'CON-123' becomes '123').
Record Data (JSON Format) The JSON object containing the fields and values to update in the record. Uses Nexoid's field naming scheme (text_ for strings, long_ for numbers, date_ for ISO datetime). Fields can be set to NULL to clear them.

Output

JSON

  • * - The JSON response from the Nexoid API representing the updated record data, excluding internal API processing time metadata.

Dependencies

  • Requires an API service account with Nexoid and credentials including customer ID, username, and password for authentication.

Troubleshooting

  • Authentication failures due to invalid credentials will throw an error 'Failed to authenticate with Nexoid API. Please enter valid API user credentials'. Verify credentials and try again.
  • Invalid JSON in the 'Record Data' field will cause an error. Ensure the JSON is correctly formatted before running the node.
  • If the Record ID includes a prefix (e.g., 'CON-123'), it is automatically stripped. Providing an incorrect or non-existent Record ID will result in API errors.

Links

Discussion