Didar CRM icon

Didar CRM

Actions for Didar CRM

Actions28

Overview

This node enables creating a new Deal entity in Didar CRM. It is useful for automating the process of adding sales opportunities or transactions into your CRM system directly from workflows. Typical scenarios include:

  • Automatically logging new deals when a lead reaches a certain stage.
  • Integrating with external systems to push deal data into Didar CRM.
  • Creating deals programmatically based on form submissions or other triggers.

For example, you could use this node to create a deal titled "Website Redesign Project" assigned to a specific owner and linked to a particular pipeline and stage, associating it with a person and company already in the CRM.

Properties

Name Meaning
Title The title 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 list (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").
Pipeline Input Mode How to specify the pipeline: select from a list or enter the pipeline ID manually.
Pipeline Pick a pipeline from a 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 stage: select from a list or enter the stage ID manually.
Pipeline Stage Pick a pipeline stage from a list (required if Stage Input Mode is "Select from list" and Pipeline Input Mode is "Select from list").
Pipeline Stage ID Enter the 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 status of the deal. Options are: Pending, Won, Lost (required).
Label IDs One or more label IDs associated with the deal (optional). Accepts multiple values via CSV, newlines, JSON array, or expressions returning an array.
Additional Fields A collection of optional fields including:
- Source ID: Identifier for the source (optional). Defaults to zero UUID.
- Source Other: Custom text for unlisted sources.
- Lost Reason ID: Identifier for lost reason. Defaults to zero UUID.
- Lost Reason Note: Additional notes about the lost reason.
- Lost Reason Other: Custom lost reason text.
- Description: Optional description of the deal.
- Creator ID: User ID of the creator; defaults to owner if empty. Defaults to zero UUID.
- Price: Deal price or amount as string. Defaults to "0".
- Visibility Type: Visibility setting for the deal. Options: Owner, Owner Group, Owner SubGroup, All. Defaults to Owner.
- Custom Fields (JSON): JSON object representing custom fields.
- Deal Items (JSON): JSON array of deal items, each with properties like ProductId, Quantity, UnitPrice, Price, Discount, Description, VariantId. Accepts JSON string or expression resolving to an array.

Output

The node outputs an array of JSON objects representing the created deal(s). Each output item contains the details of the newly created deal as returned by the Didar CRM API, including identifiers, status, associations (person, company), pipeline and stage info, labels, and any additional fields set during creation.

If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the deal, but this node focuses on JSON data output only.

Dependencies

  • Requires an active connection to Didar CRM via an API key credential configured in n8n.
  • Uses Didar CRM API endpoints to create deals.
  • Relies on dynamic loading of options for users, pipelines, stages, and other entities via internal methods (getUsers, getPipelines, getStagesForPipeline).
  • No other external dependencies are required.

Troubleshooting

  • Missing Required Fields: Errors may occur if mandatory fields like Title, Owner, Pipeline, Stage, Person ID, Company ID, or Status are missing or invalid. Ensure all required inputs are provided according to the input mode selected.
  • Invalid IDs: Manually entered IDs must be valid UUIDs recognized by Didar CRM. Invalid or non-existent IDs will cause API errors.
  • API Authentication Errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate. Verify the API key configuration.
  • Option Loading Failures: If the node cannot load options for owners, pipelines, or stages, check network connectivity and API permissions.
  • JSON Parsing Issues: For custom fields and deal items, ensure JSON strings are well-formed. Malformed JSON will cause parsing errors.
  • Status Value Errors: Only "Pending", "Won", or "Lost" are accepted for status. Using other values will result in validation errors.

Links and References

Discussion