Didar CRM icon

Didar CRM

Actions for Didar CRM

Actions28

Overview

The "Person Update" operation in this node allows users to update details of an existing person record in the Didar CRM system by specifying the person's unique identifier. This operation is useful for maintaining up-to-date contact information, organizational roles, and other personal data within a CRM workflow. For example, you might use this node to update a customer's phone number, assign a new owner to the contact, or add custom fields such as VIP status or additional email addresses.

Properties

Name Meaning
Id The unique identifier of the person to update (required).
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 How to specify 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 the owner user ID manually (required if "Enter ID manually" mode is chosen).
Additional Fields A collection of optional fields to provide more detailed information about the person:
- 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 8601 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 a 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 associated with the person.
- Zip Code Postal or ZIP code.
- Visibility Type Visibility setting for this person. Options are: Owner, Owner Group, Owner SubGroup, All.
- Custom Fields (JSON) JSON object containing custom fields as key-value pairs.
- Websites List of websites as multiple key/value pairs.
- Other Phones Additional phone numbers as multiple key/value pairs.
- Other Emails Additional emails as multiple key/value pairs.
- Addresses Addresses as multiple key/value pairs (e.g., Home, Work).
- Bank Accounts Bank account details, each entry can have up to four flexible string fields.
- Segment IDs List of segment IDs (GUIDs) to which this person belongs.

Output

The node outputs an array of JSON objects representing the updated person records. Each output item contains the updated fields reflecting the changes made during the update operation. The exact structure depends on the Didar CRM API response but typically includes identifiers, names, contact details, ownership info, and any additional fields provided.

This node does not output binary data.

Dependencies

  • Requires connection to the Didar CRM API.
  • Requires an API authentication credential configured in n8n to authorize requests.
  • Uses internal methods to load options dynamically, such as fetching users for owner selection.

Troubleshooting

  • Missing Required Fields: If the required "Id" or "Last Name" fields are missing, the node will likely throw an error. Ensure these fields are provided.
  • Invalid Owner Selection: When using "Select from list" mode for the owner, if no valid user is selected, the update may fail. Verify that the owner user exists and is correctly selected.
  • Incorrect GUID Format: Fields like Company ID, Birth Date Message ID, and Segment IDs expect GUIDs. Providing invalid formats may cause errors.
  • API Authentication Errors: If the API key or credentials are misconfigured or expired, the node will fail to connect. Check the credential setup.
  • Network Issues: Connectivity problems with the Didar CRM API endpoint can cause timeouts or failures.
  • JSON Parsing Errors: When providing custom fields as JSON, ensure the JSON syntax is correct to avoid parsing errors.

Links and References

Discussion