Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node operation creates a new "Case" entity in Didar CRM. It is useful for managing and tracking customer support issues, project tasks, or any work items that require assignment, status tracking, and categorization within the CRM system. Typical scenarios include creating a case to log a customer complaint, assign it to a responsible user, set its priority and status, and optionally link it to related entities like companies, persons, or deals.
Practical examples:
- Creating a support ticket case assigned to a specific user with a due date and priority.
- Logging an internal task case linked to a deal and setting its pipeline stage.
- Creating a completed case with a result note summarizing the outcome.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the case. This is required and represents the main identifier or summary of the case. |
| Owner Input Mode | How to specify the owner of the case: either select from a list of users or enter the owner ID manually. |
| Owner | (If Owner Input Mode is "Select from list") Select the user who will own the case. Required in this mode. |
| Owner ID | (If Owner Input Mode is "Enter ID manually") Enter the owner's user ID manually. Required in this mode. |
| Pipeline Stage ID | The ID of the pipeline stage where the case currently resides. This must be entered manually and is required. |
| Status | The current status of the case. Options are: "In Progress" or "Done". Required. |
| Users Input Mode | How to provide additional user IDs associated with the case: select multiple users from a list or enter their IDs manually. |
| Users | (If Users Input Mode is "Select from list") Select one or more users associated with the case. |
| User IDs (Manual) | (If Users Input Mode is "Enter IDs manually") Enter one or more user IDs manually. Accepts various formats including CSV, JSON array, or expressions returning arrays. |
| Result Note | A note describing the result of the case. Only shown and applicable when the status is set to "Done". |
| Additional Fields | A collection of optional fields to further describe or relate the case: |
| - Description | Optional plain-text description of the case. |
| - Company ID | Related company ID (GUID). Defaults to a zero GUID if not specified. |
| - Person ID | Related person ID (GUID). Defaults to a zero GUID if not specified. |
| - Deal ID | Related deal ID (GUID). Defaults to a zero GUID if not specified. |
| - Due Date | Due date/time for the case. If empty, defaults to the current time. |
| - Case Category | Category of the case. Options include "Activity Oriented", "Kanban", and "Ticket" with corresponding GUID values. |
| - Priority | Priority level of the case. Options are None (-2), Low (-1), Medium (0), High (1). Default is None. |
| - Other Contact IDs | Additional related contact IDs (GUIDs). Can accept multiple values. |
| - Custom Fields | JSON object representing custom fields to set on the case. |
| - Label IDs | Label IDs to assign to the case. Can accept multiple values. |
| - Visibility Type | Visibility setting for the case. Options are "Owner", "Owner Group", "Owner SubGroup", and "All". Default is "Owner". |
Output
The node outputs an array of JSON objects representing the created case(s). Each output item contains the details of the newly created case as returned by the Didar CRM API. The structure typically includes all standard and custom fields set during creation, such as the case ID, title, owner, status, pipeline stage, related entities, and any additional metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Didar CRM via an API key credential configured in n8n.
- The node depends on Didar CRM's API endpoints for cases, including user and pipeline stage lookups.
- Some input options (like selecting users) rely on dynamic loading methods that fetch available users from the CRM.
Troubleshooting
- Missing required fields: Errors may occur if mandatory fields like Title, Pipeline Stage ID, or Status are missing. Ensure these are provided.
- Invalid user or pipeline stage IDs: Manually entered IDs must be valid GUIDs recognized by the CRM. Invalid IDs will cause API errors.
- Incorrect JSON in custom fields: The "Custom Fields (JSON)" property must be valid JSON. Malformed JSON will cause parsing errors.
- Permission issues: The API key used must have sufficient permissions to create cases and assign owners/users.
- Status-dependent fields: The "Result Note" field only applies when Status is "Done". Setting it otherwise may be ignored or cause warnings.
Links and References
- Didar CRM official documentation (for API and entity definitions)
- n8n documentation on creating custom nodes and using credentials
- JSON formatting guides for custom fields input