Didar CRM icon

Didar CRM

Actions for Didar CRM

Actions28

Overview

This node enables creating a new person record in Didar CRM. It is useful for automating the addition of contacts or leads into your CRM system, ensuring that all relevant personal and contact information is captured efficiently. Typical scenarios include onboarding new clients, importing contacts from other systems, or integrating form submissions directly into the CRM.

For example, you can use this node to create a person with their first and last name, assign an owner user, add multiple phone numbers and emails, specify company affiliation, and set custom fields or visibility settings.

Properties

Name Meaning
First Name Optional given name of the person.
Last Name Required family name (last name) of the person.
Mobile Phone Primary mobile phone number.
Work Phone Work phone number.
Owner Input Mode Choose how to set the owner of this person: either select from a list of users or enter the owner ID manually.
Owner Select the owner user from a list (required if "Select from list" mode is chosen).
Owner ID Enter owner user ID manually (required if "Enter ID manually" mode is chosen).
Additional Fields A collection of optional extra fields including:
- Title Honorific or title (e.g., Mr., Ms., Dr.).
- Company Name Related company name as plain text.
- Company ID Related company ID (GUID). Defaults to a zero GUID if not specified.
- Birth Date (ISO) Birth date in ISO format (e.g., 2025-08-31T08:02:06Z).
- Birth Date Message ID Notification/message template ID for birthday (GUID). Defaults to a zero GUID if not specified.
- Work Phone Extension Extension number for the work phone.
- Fax Fax number.
- Email Primary email address.
- Is VIP Boolean flag to mark this person as VIP.
- Background Info Notes or background information about the person.
- Position Job title or position.
- Customer Code Internal or CRM customer code.
- National Code National ID code.
- Zip Code Postal/ZIP code.
- Visibility Type Visibility setting for this person. Options are: Owner, Owner Group, Owner SubGroup, All.
- Custom Fields (JSON) JSON object representing custom fields with key-value pairs.
- Websites List of websites as key/value pairs (multiple entries allowed).
- Other Phones Additional phone numbers as key/value pairs (multiple entries allowed).
- Other Emails Additional emails as key/value pairs (multiple entries allowed).
- Addresses Addresses as key/value pairs (e.g., Home, Work) (multiple entries allowed).
- Bank Accounts Bank account details with four flexible string fields per entry (multiple entries allowed).
- Segment IDs List of segment IDs (GUIDs) to associate with the person. Multiple values allowed.

Output

The node outputs an array of JSON objects representing the created person records. Each output item contains the full data of the newly created person as returned by the Didar CRM API, including all standard and additional fields provided during creation.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to Didar CRM via an API key credential configured in n8n.
  • The node depends on the Didar CRM API endpoints for person creation.
  • The "Owner" selection options are dynamically loaded from the CRM's user list.

Troubleshooting

  • Missing required fields: The "Last Name" field is mandatory. Omitting it will likely cause an error from the API.
  • Invalid Owner ID: If entering the owner ID manually, ensure the ID is valid and exists in the CRM; otherwise, the API may reject the request.
  • Incorrect JSON in Custom Fields: The "Custom Fields (JSON)" property must be valid JSON. Malformed JSON will cause parsing errors.
  • API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions to create persons.
  • Date Format Issues: The birth date must be in ISO 8601 format; incorrect formatting may lead to rejection.
  • GUID Defaults: Some fields default to a zero GUID if left empty; verify if this is acceptable or if actual GUIDs should be provided.

Links and References

Discussion