Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Activity → Search
AI-generatedOverview
The node provides an integration with Didar CRM to search for activities based on various filters. It allows users to query activities by specifying criteria such as activity types, owners, contacts, deals, cases, creators, date ranges, completion status, deletion status, tags, and pagination options. This is useful in scenarios where you want to retrieve a filtered list of activities from the CRM system for reporting, automation, or further processing.
For example, you could use this node to:
- Retrieve all completed activities of certain types owned by a specific user within a date range.
- Search for activities related to a particular deal or case.
- Fetch activities tagged with specific tags and limit the number of results returned.
Properties
| Name | Meaning |
|---|---|
| Activity Types Input Mode | Choose how to provide activity type IDs: either select multiple types from a list or enter their IDs manually. |
| Activity Types | Select one or more activity types from a dynamically loaded list (optional filter). |
| Activity Type IDs (Manual) | Enter activity type IDs manually as CSV, JSON array, or multi-line input (optional filter). |
| Owner Input Mode | Choose how to specify the owner filter: select from a list or enter the owner ID manually (optional). |
| Owner | Select the owner user from a dynamically loaded list (optional filter). |
| Owner ID | Enter the owner user ID manually (optional filter). |
| Contact IDs | Provide contact IDs as CSV, JSON array, or multi-line input to filter activities related to these contacts. |
| Deal ID | Filter activities related to a specific deal by its ID (optional). |
| Case ID | Filter activities related to a specific case by its ID (optional). |
| Creator Input Mode | Choose how to specify the creator filter: select from a list or enter the creator ID manually (optional). |
| Creator | Select the creator user from a dynamically loaded list (optional filter). |
| Creator ID | Enter the creator user ID manually (optional filter). |
| Additional Filters | A collection of optional filters including: |
| - From Date | Lower bound date/time for filtering activities. Defaults to very early date if not set. |
| - To Date | Upper bound date/time for filtering activities. Defaults to far future date if not set. |
| - Is Done | Filter by completion flag: Not set, True (1), or False (-1). |
| - Is Deleted | Filter by deletion flag: Not set, True (1), or False (-1). |
| - Tag IDs | Tag IDs as CSV, JSON array, or multi-line input to filter activities by tags. |
| - From | Offset for pagination (default 0). |
| - Limit | Number of results to return (default 10). |
Output
The node outputs an array of activity objects matching the specified filters. Each item in the output json field represents an activity record retrieved from Didar CRM. The structure of each activity object depends on the CRM's API response but typically includes fields like activity ID, type, owner, related contacts/deals/cases, creator, timestamps, status flags, and tags.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- Uses dynamic option loading methods to fetch lists of activity types and users for selection inputs.
- The node relies on Didar CRM's API endpoints to perform the search operation.
Troubleshooting
- Empty Results: If no activities are returned, verify that the filter criteria are correct and that there are matching records in the CRM.
- Invalid IDs: Manually entered IDs (for activity types, owners, creators, contacts, etc.) must be valid and exist in the CRM; otherwise, the search may fail or return no results.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions to access activity data.
- Pagination Issues: If too many results are expected, adjust the "Limit" property accordingly; some APIs may have maximum limits per request.
- Date Format: Ensure date/time values are in ISO 8601 format as required by the node.
Links and References
- Didar CRM Official Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- ISO 8601 Date and Time Format