Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node operation allows you to create a new company record in the Didar CRM system. It is useful for automating the addition of company data into your CRM, such as when onboarding new clients or partners, syncing external databases, or integrating lead generation tools.
Practical examples include:
- Automatically creating company entries from web form submissions.
- Importing company data from other systems or spreadsheets.
- Adding companies programmatically during sales or marketing workflows.
Properties
| Name | Meaning |
|---|---|
| Name | 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 provide more details about 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 emails 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 created company records. Each output item contains the full details of the newly created company as returned by the Didar CRM API, including all standard and additional fields set during creation.
If the node supports binary data output, it would typically represent attachments or documents related to the company, but this operation focuses on JSON data only.
Dependencies
- Requires connection to the Didar CRM API via an API key credential configured in n8n.
- The node uses internal methods to load options dynamically, such as fetching the list of users for owner selection.
- Proper API permissions are needed to create company records.
Troubleshooting
- Missing required fields: The "Name" property is mandatory. Omitting it will likely cause an error from the API.
- Invalid owner specification: If "Owner Input Mode" is set to select but no owner is chosen, or if manual mode is selected but the owner ID is invalid or missing, the operation may fail.
- Malformed JSON in custom fields: The "Custom Fields (JSON)" must be valid JSON; otherwise, parsing errors can occur.
- API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues can cause failures; retrying later may help.
Links and References
- Didar CRM API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- JSON Syntax Guide