Digitaliso icon

Digitaliso

Consume Digitaliso API.

Overview

The Digitaliso node for n8n allows you to interact with the Digitaliso API, specifically managing "Items". The Update Item operation (corresponding to HTTP PUT) lets you update an existing item by specifying its ID and providing new values for its fields. This is useful in workflows where you need to programmatically modify records in your Digitaliso system, such as updating inventory details, user information, or other managed entities.

Example scenarios:

  • Automatically updating product information when changes are detected in another system.
  • Synchronizing item data between Digitaliso and external databases.
  • Batch-updating multiple items based on business logic.

Properties

Name Type Meaning
Items string Specifies the type of items or endpoint segment to run the API on (e.g., "products").
ID number The unique identifier of the item to update.
Body Parameters fixedCollection Key-value pairs representing the fields and their new values to update in the item.

Output

  • The output is a JSON object containing the response from the Digitaliso API after updating the item.
  • If the operation is successful, the response will typically include the updated item's data.
  • In case of errors (and if "Continue On Fail" is enabled), the output may contain an error field with the error message.

Example output:

{
  "id": 123,
  "name": "Updated Item Name",
  "status": "active"
}

Note: The actual structure depends on the specific item type and API response.


Dependencies

  • External Service: Requires access to the Digitaliso API at https://api.qsa.net/v1/.
  • API Credentials: You must provide valid digitalisoApi credentials (API key and company).
  • n8n Configuration: No special environment variables beyond standard credential setup.

Troubleshooting

Common Issues:

  • Invalid Credentials: If the API key or company is incorrect, authentication will fail.
  • Missing Required Fields: Not providing the required "ID" or necessary body parameters will result in errors.
  • Incorrect Endpoint ("Items"): Supplying an invalid value for "Items" can cause the request to fail.
  • API Errors: Any server-side validation errors (e.g., trying to update a non-existent item) will be returned as error messages.

Error Messages:

  • "401 Unauthorized": Check your API key and company credentials.
  • "400 Bad Request": Ensure all required fields and correct parameter names/values are provided.
  • "404 Not Found": The specified item ID does not exist.
  • "error": "<message>": When "Continue On Fail" is enabled, errors are returned in the output under the error field.

Links and References

Discussion