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 enabling operations on various CRM resources. For the Person resource with the Search operation, it allows users to perform a filtered search for person records within the CRM system. This is useful when you want to find contacts or leads based on keywords, ownership, time ranges, and other custom filters.
Typical use cases include:
- Searching for persons matching certain keywords or criteria.
- Filtering persons owned by specific users.
- Retrieving recently added or alphabetically sorted persons.
- Applying advanced filters such as deletion status, pinned status, VIP status, and custom JSON-based field filters.
- Limiting the number of results returned.
This operation helps automate workflows that require dynamic retrieval of contact data from Didar CRM, such as syncing contacts, generating reports, or triggering follow-up actions.
Properties
| Name | Meaning |
|---|---|
| Keywords | Free-text search input to match against person records (optional). |
| Owner Input Mode | Method to specify the owner filter: either select an owner from a list or enter the owner ID manually (optional). |
| Owner | Select the owner user from a dropdown list to filter persons by ownership (optional; shown if Owner Input Mode is "Select from list"). |
| Owner ID | Enter the owner user ID manually to filter persons by ownership (optional; shown if Owner Input Mode is "Enter ID manually"). |
| Additional Filters | Collection of optional filters including: • Search From Time: Lower bound datetime for filtering. • Search To Time: Upper bound datetime for filtering. • Sort Order: Alphabetical or Newest First. • Is Deleted: Filter by deletion flag. • Is Pinned: Filter by pin flag. • Is VIP: Filter by VIP flag. • Custom Fields (JSON): JSON array of custom field filters. • Limit: Number of results to return. |
Output
The node outputs an array of person objects in the json output field. Each object represents a person record matching the search criteria, containing all relevant fields retrieved from Didar CRM.
If binary data were involved (not indicated here), it would typically represent attachments or files related to the person, but this operation focuses on JSON data only.
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 person records.
- Uses internal methods to load options dynamically, e.g., loading users for the owner selection dropdown.
Troubleshooting
- Empty results: Ensure the search filters are not too restrictive. Check keyword spelling and date ranges.
- Invalid owner ID: When entering owner ID manually, verify the ID exists in Didar CRM.
- API authentication errors: Confirm the API key credential is valid and has sufficient permissions.
- Malformed JSON in Custom Fields: If using the JSON filter, ensure it is correctly formatted JSON array.
- Rate limits or connectivity issues: Check network access and Didar CRM API rate limits.
Links and References
- Didar CRM official API documentation (refer to your organization's API docs).
- n8n documentation on creating and configuring API credentials.
- JSON formatting guides for constructing custom field filters.