Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node enables searching for companies within the Didar CRM system. It allows users to perform a free-text search and apply various filters to narrow down the list of companies returned. This is useful in scenarios where you want to find specific companies based on keywords, ownership, status flags (like VIP or pinned), or custom fields. For example, you might use this node to retrieve all companies owned by a particular user that were created within a certain date range, or to find companies marked as VIP.
Properties
| Name | Meaning |
|---|---|
| Keywords | Free-text search string to match company records (optional). |
| Owner Input Mode | Method to specify the owner filter: either select from a list of users or enter an owner ID manually. |
| Owner | Select the owner user from a dropdown list (shown if "Owner Input Mode" is "Select from list"). |
| Owner ID | Enter the owner user ID manually (shown if "Owner Input Mode" is "Enter ID manually"). |
| Additional Filters | Collection of optional filters including: |
| - Search From Time | Lower bound datetime filter for the selected time field. |
| - Search To Time | Upper bound datetime filter for the selected time field. |
| - Sort Order | Sorting mode for results: Alphabetical or Newest First. |
| - Is Deleted | Filter by deletion flag: Not set, No, or Yes. |
| - Is Pinned | Filter by pin flag: Not set, True, or False. |
| - Is VIP | Filter by VIP flag: Not set, True, or False. |
| - Custom Fields (JSON) | JSON array specifying custom field filters (optional). |
| - Limit | Number of results to return (default 10). |
Output
The node outputs an array of company objects matching the search criteria in the json field of each output item. Each object contains the company's data as retrieved from the Didar CRM API, including standard fields and any custom fields present. The output does not include binary data.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- The node depends on the Didar CRM API being accessible and properly authenticated.
- Uses internal methods to load options such as user lists for owner selection.
Troubleshooting
- Empty Results: If no companies are returned, verify that the search keywords and filters are correct and that the user has access rights to the requested data.
- Invalid Owner ID: When entering owner ID manually, ensure the ID is valid; otherwise, the filter will be ignored or cause no matches.
- Date Filters: Ensure date/time values are correctly formatted ISO strings; invalid dates may cause errors or unexpected filtering.
- API Errors: Authentication failures or network issues with Didar CRM API will result in errors. Check API credentials and connectivity.
- Custom Fields JSON: Malformed JSON in the custom fields filter can cause parsing errors. Validate JSON syntax before input.
Links and References
- Didar CRM Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General info on ISO 8601 Date Format