Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
The node provides integration with Didar CRM, specifically supporting a variety of resources and operations. For the Supplementary resource with the Didaryab Searching operation, it performs a search across multiple entity types within Didar CRM based on a user-provided keyword.
This operation is useful when you want to quickly find relevant records in Didar CRM that match a specific search term, spanning contacts, companies, deals, cases, or attachments. For example, if you have a customer name or a deal reference and want to locate all related entities in one go, this search can help aggregate those results efficiently.
Practical scenarios include:
- Quickly retrieving all CRM entities related to a client or project keyword.
- Aggregating search results for reporting or further automation workflows.
- Triggering follow-up actions based on found entities.
Properties
| Name | Meaning |
|---|---|
| Keyword | The search term used to query Didar CRM entities. This is a required string input. |
| Types | One or more entity types to include in the search. Options: Contact, Company, Deal, Case, Attachment. Defaults to all selected. |
Output
The output is an array of JSON objects representing the search results from Didar CRM. Each object corresponds to an entity matching the keyword within the specified types. The exact structure depends on the entity type but generally includes identifying fields such as IDs, names, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- The node depends on Didar CRM's API endpoints for searching supplementary data.
- Proper network access and authentication must be set up for successful API calls.
Troubleshooting
- Empty Results: If no results are returned, verify that the keyword is correct and that the selected types actually contain matching data.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to perform searches.
- API Rate Limits: Frequent or large searches might hit API rate limits; consider adding delays or reducing search scope.
- Invalid Property Values: Make sure the "Types" property contains valid options; invalid values may cause errors.
- Network Issues: Check connectivity to Didar CRM API endpoints.
Common error messages might relate to authentication failure, invalid parameters, or network timeouts. Resolving these typically involves checking credentials, input correctness, and network status.
Links and References
- Didar CRM Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General API Authentication Best Practices
Note: Internal credential names and implementation details have been omitted per guidelines.