Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node integrates with Didar CRM to perform various actions on different entities within the CRM system. Specifically, for the Company resource and the Get operation, it fetches detailed information about a company by its unique identifier. This is useful when you need to retrieve up-to-date company data from Didar CRM to use in workflows such as customer management, reporting, or synchronization with other systems.
Practical examples:
- Automatically retrieving company details when a new deal is created.
- Enriching contact records with company information during lead qualification.
- Fetching company data to display in dashboards or reports.
Properties
| Name | Meaning |
|---|---|
| Company Id | The unique identifier of the company to fetch (required). |
Output
The node outputs JSON data representing the company details retrieved from Didar CRM. The structure typically includes all relevant fields of the company record, such as name, address, contact info, and any custom fields defined in the CRM.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but for this operation, the output is purely JSON.
Dependencies
- Requires an API key credential for authenticating with Didar CRM.
- Needs network access to the Didar CRM API endpoint.
- No additional environment variables are explicitly required based on the static code analysis.
Troubleshooting
Common issues:
- Invalid or missing Company Id: The node requires a valid company identifier; ensure this is provided and correct.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network connectivity problems: Ensure the n8n instance can reach the Didar CRM API.
Common error messages:
- "Company not found": Occurs if the provided Company Id does not exist in Didar CRM.
- "Authentication failed": Indicates issues with the API key or credentials.
- Timeout or connection errors: Suggest network or API availability problems.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring stable network connections.
Links and References
- Didar CRM Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- Didar CRM API Reference (replace with actual URL)