Didar CRM icon

Didar CRM

Actions for Didar CRM

Actions28

Overview

This node operation updates an existing product in the Didar CRM system. It allows users to modify various attributes of a product such as its title, internal code, category, pricing, variants, and custom fields. This is useful for keeping product information current, correcting errors, or adjusting details like pricing or availability.

Typical use cases include:

  • Updating product details after a price change.
  • Adding or modifying product variants.
  • Changing the product's category or unit of measurement.
  • Activating or deactivating products based on availability.
  • Enriching product data with custom fields for specialized workflows.

Properties

Name Meaning
Product ID The unique identifier of the product to update. Required.
Title The name/title of the product. Required.
Code Internal product code used for identification (optional).
Product Category Selectable category for the product (optional). Loaded dynamically from available categories.
Unit Unit name representing measurement or currency (e.g., USD, item, box).
Unit Price Base price of the product, supporting decimal precision up to 10 digits.
Variants JSON array of variant objects. Each variant can include an "Id" if updating existing variants. Example: [{ "Id": "<GUID>", "Title": "V1", "VariantCode": "A1", "UnitPrice": 1000 }, { "Id": "<GUID>", "Title": "V2", "VariantCode": "A2", "UnitPrice": 0 }]
Active Boolean flag indicating whether the product is active or inactive.
Description Optional textual description of the product.
Custom Fields (JSON) JSON object containing custom field key-value pairs for additional product metadata.

Output

The node outputs an array of JSON objects representing the updated product(s). Each output item contains the updated product data as returned by the Didar CRM API, including all standard and custom fields that were set or modified.

If the product has variants, these are included within the product data structure.

No binary data output is produced by this operation.

Dependencies

  • Requires connection to Didar CRM via an API key credential configured in n8n.
  • The node depends on dynamic loading of product categories for selection, which requires proper API access.
  • Network connectivity to the Didar CRM API endpoint is necessary.

Troubleshooting

  • Missing or invalid Product ID: The update operation requires a valid product ID. Ensure the ID is correct and corresponds to an existing product.
  • Invalid JSON in Variants or Custom Fields: If the JSON provided for variants or custom fields is malformed, the node will fail. Validate JSON syntax before execution.
  • API Authentication Errors: If the API key credential is missing, expired, or incorrect, authentication will fail. Verify credentials in n8n settings.
  • Permission Issues: Insufficient permissions in Didar CRM may prevent updating products. Confirm user rights allow product modifications.
  • Network or Timeout Errors: Connectivity issues can cause failures. Check network status and retry if needed.

Links and References

Discussion