Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node updates an existing company record in the Didar CRM system. It is useful when you need to modify details of a company such as its name, contact information, ownership, visibility settings, and various custom fields. Typical scenarios include keeping company data current after changes in contact info, ownership, or status, or enriching company records with additional metadata like VIP status or segment IDs.
For example, you might use this node to update a company's phone numbers and email addresses after receiving new contact details from a client, or to mark a company as VIP for special handling in your sales process.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the company to update (required). |
| FirstName | The name of the company (required). |
| Mobile Phone | Primary mobile phone number of the company. |
| Work Phone | Work phone number of the company. |
| Owner Input Mode | How to specify the owner of the company: either select from a list of users or enter an ID manually. Options: "Select from list", "Enter ID manually". |
| Owner | Select the owner user from a list (required if Owner Input Mode is "Select from list"). |
| Owner ID | Enter the owner user ID manually (required if Owner Input Mode is "Enter ID manually"). |
| Additional Fields | A collection of optional fields to further describe the company: |
| - Work Phone Extension | Extension number for the work phone. |
| - Fax | Fax number. |
| Primary email address. | |
| - Is VIP | Boolean flag to mark the company as VIP. |
| - Background Info | Notes or background information about the company. |
| - Customer Code | Internal or CRM-specific customer code. |
| - Economic Issue | Company-specific economic issue code. |
| - Registration Number | Company registration number. |
| - National ID | Company national identification number. |
| - Zip Code | Postal or ZIP code. |
| - Visibility Type | Visibility setting for the company record. Options: "Owner", "Owner Group", "Owner SubGroup", "All". |
| - Custom Fields (JSON) | JSON object containing custom fields with key-value pairs. |
| - Websites | List of websites as key/value pairs (e.g., main site, partner site). |
| - Other Phones | Additional phone numbers as key/value pairs. |
| - Other Emails | Additional email addresses as key/value pairs. |
| - Addresses | Addresses as key/value pairs (e.g., HQ, branch). |
| - Bank Accounts | Bank account details with up to four flexible fields per entry. |
| - Segment IDs | List of segment IDs (GUIDs) associated with the company. |
Output
The node outputs an array of JSON objects representing the updated company data returned by the Didar CRM API. Each output item corresponds to one input item processed and contains the updated company record fields as confirmed by the API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the company, but this node focuses on JSON data only.
Dependencies
- Requires connection to the Didar CRM API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- Uses internal methods to load options dynamically, e.g., fetching users for owner selection.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like "Id" or "FirstName" are not provided. Ensure these are set.
- Invalid Owner Selection: If "Owner Input Mode" is set to select but no owner is chosen, or manual mode is selected but the ID is invalid, the update will fail.
- API Authentication Errors: If the API key or token is missing or invalid, authentication errors will be returned. Verify credentials in n8n.
- Malformed JSON in Custom Fields: Providing invalid JSON in the "Custom Fields (JSON)" property can cause parsing errors. Validate JSON syntax before submitting.
- Network Issues: Connectivity problems with the Didar CRM API endpoint will prevent updates. Check network access and API availability.
Links and References
- Didar CRM official API documentation (refer to your organization's API docs).
- n8n documentation on creating and configuring custom nodes.
- JSON validation tools for verifying custom fields input.