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 deals within their CRM database. The "Search" operation under the "Deal" resource allows filtering deals based on various criteria such as keywords, status, owner, associated contacts, labels, pipeline stages, and additional custom filters. This node is useful for automating workflows that require retrieving deal information matching specific conditions, such as generating reports, syncing data with other systems, or triggering actions based on deal statuses.
Practical examples:
- Retrieve all deals owned by a particular user that are currently pending.
- Search deals within a specific pipeline stage and filter by probability or date ranges.
- Find deals linked to certain contacts or labeled with specific tags.
- Sort deals by creation time or follow-up times to prioritize outreach.
Properties
| Name | Meaning |
|---|---|
| Keywords | Free-text search term to find deals matching the input text (optional). |
| Status | Filter deals by their status. Options: Not set, Pending, Won, Lost. |
| Owner Input Mode | Choose how to specify the owner filter: select from a list of users or enter the owner ID manually (optional). |
| Owner | Select the owner user from a dropdown list (shown if Owner Input Mode is "select"). Leave empty to ignore this filter. |
| Owner ID | Enter the owner user ID manually (shown if Owner Input Mode is "manual"). Leave empty to ignore this filter. |
| Contact IDs | One or more contact IDs to filter deals by associated contacts. Accepts multiple values via CSV, newlines, JSON array, or expressions (optional). |
| Label IDs | One or more label IDs to filter deals by assigned labels. Accepts multiple values via CSV, newlines, JSON array, or expressions (optional). |
| Pipeline Input Mode | Choose how to specify pipeline and stage filters: select from lists or enter IDs manually. Both pipeline and stage must be provided together or both left empty (optional). |
| Pipeline | Select a pipeline from a list (required if stage is set; optional otherwise). |
| Pipeline Stage | Select a stage within the chosen pipeline (required if pipeline is set; optional otherwise). |
| Pipeline ID (Manual) | Enter pipeline ID manually (required if stage manual is set; optional otherwise). |
| Pipeline Stage ID (Manual) | Enter pipeline stage ID manually (required if pipeline manual is set; optional otherwise). |
| Additional Filters | Collection of optional filters including: |
| - Search From Time: Lower bound datetime for filtering by selected time field. | |
| - Search To Time: Upper bound datetime for filtering by selected time field. | |
| - Sort By: Sorting mode with options like Created Time, Last Follow-up Time, Next Follow-up Time, Has Proforma Invoice, Has Invoice, No Invoice, Has Canceled Invoice, Has Proforma With Price, Has Proforma Without Price, Won Time, Next Activity Time. | |
| - Probability: Numeric filter for deal probability percentage (0–100). | |
| - Next Activity From / To: Date range filters for next activity time (optional). | |
| - Source ID: Filter by source identifier (optional). | |
| - Lost Reason ID: Filter by lost reason identifier (optional). | |
| - Custom Fields (JSON): JSON array of custom field filters (optional). | |
| - Limit: Number of results to return (default 10). |
Output
The node outputs an array of deal objects in the json output field. Each object represents a deal matching the search criteria and includes its properties as returned by the Didar CRM API. The exact structure depends on the CRM's deal schema but typically contains fields such as deal ID, name, status, owner, pipeline info, probability, timestamps, and any custom fields.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- Uses Didar CRM API endpoints to perform deal searches.
- Load options for dynamic dropdowns (e.g., users, pipelines, stages) depend on API calls to Didar CRM.
- Proper API permissions are needed to read deal data and related entities.
Troubleshooting
- Empty results: Verify that the filter criteria are correct and that the account has deals matching those filters. Check if required fields like pipeline and stage are both set when using pipeline filters.
- Invalid owner or pipeline IDs: When entering IDs manually, ensure they are valid and exist in the CRM.
- API authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- Rate limits or API errors: If the CRM API returns rate limit errors or other failures, consider adding retry logic or reducing request frequency.
- Incorrect JSON in Custom Fields: Ensure the JSON array for custom field filters is well-formed and matches expected schema.
Links and References
- Didar CRM official documentation (for API details and entity schemas)
- n8n documentation on creating and configuring credentials
- General REST API usage best practices