Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
The node provides an integration with Didar CRM, specifically enabling users to search for cases within the CRM system. The "Case Search" operation allows filtering and retrieving case records based on various criteria such as keywords, owner, time range, contact IDs, custom fields, and result limits.
This node is beneficial in scenarios where you want to automate workflows involving case management, such as:
- Retrieving cases related to a specific user or owner.
- Searching cases created or updated within a certain time frame.
- Filtering cases by associated contacts or custom field values.
- Limiting the number of returned cases for performance or pagination purposes.
For example, a support team could use this node to automatically fetch all open cases assigned to a particular agent within the last month, then trigger follow-up actions like notifications or reporting.
Properties
| Name | Meaning |
|---|---|
| Keywords | Free-text search string to filter cases by matching text content (optional). |
| Owner Input Mode | Method to specify the owner filter: either select from a list of users or enter the owner ID manually (optional). |
| Owner | When "Select from list" mode is chosen, pick the owner user from a dynamically loaded list (optional). |
| Owner ID | When "Enter ID manually" mode is chosen, provide the owner user ID as a string (optional). |
| Additional Filters | A collection of optional filters including: • Search From Time: Lower bound datetime for filtering cases. • Search To Time: Upper bound datetime. • Contact IDs: One or more contact IDs to filter by. • Custom Fields (JSON): JSON array specifying custom field filters. • Limit: Number of results to return (default 10). |
Output
The node outputs an array of case objects in the json output field. Each object represents a case record matching the search criteria, containing relevant case data as provided by the Didar CRM API.
If binary data were involved (not indicated here), it would typically represent attachments or files related to cases, but this operation focuses on JSON data only.
Dependencies
- Requires an active connection to Didar CRM via an API key credential configured in n8n.
- The node depends on the Didar CRM API endpoints for searching cases.
- Dynamic loading of user options for the owner filter requires proper API access permissions.
Troubleshooting
- Empty Results: If no cases are returned, verify that the search criteria are correct and that there are matching cases in the CRM. Check date ranges and owner filters carefully.
- Invalid Owner ID: When entering owner ID manually, ensure the ID is valid and exists in the CRM; otherwise, the search may fail or return no results.
- API Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to perform case searches.
- Malformed Custom Fields JSON: If using the custom fields filter, ensure the JSON syntax is correct; invalid JSON will cause errors.
- Rate Limits or Timeouts: Large queries or high-frequency requests might hit API rate limits; consider reducing the limit or adding delays.
Links and References
- Didar CRM Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- JSON Syntax Guide