Didar CRM icon

Didar CRM

Actions for Didar CRM

Actions28

Overview

This node operation updates an existing Deal entity in Didar CRM by its unique identifier. It allows users to modify various attributes of a deal such as title, owner, pipeline, stage, related person and company, status, labels, pricing, visibility, and custom fields.

Typical use cases include:

  • Adjusting deal details after receiving new information.
  • Changing the deal's pipeline stage as it progresses through sales stages.
  • Updating ownership or visibility settings when team responsibilities change.
  • Adding or modifying custom fields or deal items for detailed tracking.

For example, a sales automation workflow could update a deal’s status to "Won" and move it to the final pipeline stage once payment is confirmed.

Properties

Name Meaning
Id The unique identifier of the deal to update (required).
Title The title or name of the deal (required).
Owner Input Mode How to specify the deal owner: either select from a list of users or enter the owner ID manually.
Owner Select the deal owner from a loaded list of users (required if Owner Input Mode is "Select from list").
Owner ID Enter the owner ID manually (required if Owner Input Mode is "Enter ID manually").
Label IDs One or more label IDs associated with the deal (optional). Accepts multiple values via CSV, newlines, JSON array, or expressions returning arrays.
Pipeline Input Mode How to specify the pipeline: select from a list or enter the pipeline ID manually.
Pipeline Pick a pipeline from a loaded list (required if Pipeline Input Mode is "Select from list").
Pipeline ID Enter the pipeline ID manually (required if Pipeline Input Mode is "Enter ID manually").
Stage Input Mode How to specify the pipeline stage: select from a list or enter the stage ID manually.
Pipeline Stage Pick a pipeline stage from a loaded list depending on the selected pipeline (required if Stage Input Mode is "Select from list").
Pipeline Stage ID Enter the pipeline stage ID manually (required if Stage Input Mode is "Enter ID manually").
Person ID The ID of the person related to the deal (required). Defaults to a zero UUID if not specified.
Company ID The ID of the company related to the deal (required). Defaults to a zero UUID if not specified.
Status The current status of the deal. Options are: Pending, Won, Lost (required).
Additional Fields A collection of optional fields including:
- Source ID: Identifier for the source of the deal.
- Source Other: Custom text for other/unlisted sources.
- Lost Reason ID: Identifier for why the deal was lost.
- Lost Reason Note: Additional notes about the lost reason.
- Lost Reason Other: Custom text for lost reason.
- Description: Optional textual description of the deal.
- Creator ID: User ID of the creator; defaults to owner if empty.
- Price: The monetary value or amount of the deal.
- Visibility Type: Controls who can see the deal. Options: Owner, Owner Group, Owner SubGroup, All.
- Custom Fields (JSON): JSON object representing custom fields for the deal.
- Deal Items (JSON): JSON array describing deal items, each with product ID, quantity, unit price, discount, description, variant ID, etc. Accepts JSON string or expression resolving to an array.

Output

The node outputs an array of JSON objects representing the updated deal(s). Each output item contains the full details of the deal after the update, reflecting all changes made.

If the deal includes binary data (not indicated here), it would be included accordingly, but this operation primarily deals with JSON data.

Dependencies

  • Requires an active connection to Didar CRM via an API key credential configured in n8n.
  • Uses API endpoints to fetch dynamic options for users, pipelines, and pipeline stages.
  • The node depends on proper permissions in Didar CRM to update deals and access related entities like users, pipelines, persons, and companies.

Troubleshooting

  • Missing Required Fields: Errors may occur if required fields like Deal Id, Title, Person ID, or Company ID are missing or invalid. Ensure these are correctly provided.
  • Invalid IDs: Manually entered IDs for owner, pipeline, or stage must be valid UUIDs recognized by Didar CRM. Invalid IDs will cause update failures.
  • Permission Denied: If the API key lacks permission to update deals or access certain resources, the node will fail. Verify API credentials and user permissions.
  • Incorrect JSON Format: For custom fields or deal items, invalid JSON syntax will cause errors. Validate JSON input before running.
  • Dependency Loading Failures: Dynamic option loading for users, pipelines, or stages requires network connectivity and valid credentials. Failure to load options may indicate configuration issues.

Links and References

Discussion