Didar CRM

Overview

This node integrates with Didar CRM to perform various actions on different entities. Specifically, for the Person - Get operation, it fetches detailed information about a person using their unique Person Id. This is useful when you need to retrieve up-to-date contact or profile data of a specific individual stored in the CRM.

Common scenarios include:

• Retrieving a person's details before sending personalized communications.
• Fetching contact info to enrich customer support tickets.
• Integrating CRM data into other workflows or databases.

Example: Given a Person Id, the node returns all available data about that person from Didar CRM, enabling further processing or decision-making in your automation.

Properties

Output

The node outputs an array of JSON objects representing the person’s data as retrieved from Didar CRM. The structure typically includes fields such as name, contact details, company affiliation, and any custom attributes defined in the CRM.

If the node supports binary data output (not indicated here), it would represent attachments or files related to the person, but this operation primarily returns JSON data.

Dependencies

• Requires an active connection to Didar CRM via an API key credential configured in n8n.
• The node depends on Didar CRM's API being accessible and the provided Person Id being valid.

Troubleshooting

• Invalid Person Id: If the Person Id does not exist or is malformed, the node may return an error or empty result. Verify the Person Id is correct.
• Authentication Errors: Ensure the API key credential is correctly set up and has permissions to read person data.
• Network Issues: Connectivity problems with Didar CRM API can cause timeouts or failures.
• API Limits: Exceeding rate limits imposed by Didar CRM could lead to temporary blocking; check API usage policies.

Links and References

• Didar CRM Official Documentation (replace with actual URL)
• n8n Documentation on Creating Custom Nodes