Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node operation updates an existing case in Didar CRM. It allows users to modify various attributes of a case such as its title, owner, pipeline stage, status, related entities (company, person, deal), priority, visibility, and custom fields. This is useful for workflows that need to keep case information current based on external triggers or data changes.
Practical examples include:
- Automatically updating the status and owner of a support ticket when it progresses through different stages.
- Changing the priority or adding notes to a case after receiving new information.
- Linking a case to different contacts or deals dynamically during a sales process.
Properties
| Name | Meaning |
|---|---|
| Case ID | The unique identifier of the case to update. Required. |
| Title | The title of the case. Required. |
| Owner Input Mode | How to specify the owner user: either select from a list or enter the owner ID manually. |
| Owner | Select the owner user from a list (required if "Select from list" mode is chosen). |
| Owner ID | Enter the owner user ID manually (required if "Enter ID manually" mode is chosen). |
| Pipeline Stage ID | The ID of the pipeline stage to assign the case to. Must be entered manually. Required. |
| Status | The 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 from a list or enter IDs manually. |
| Users | Select one or more users from a list (required if "Select from list (multi)" mode is chosen). |
| User IDs (Manual) | Enter one or more user IDs manually. Accepts multiple formats including CSV, JSON array, or expressions returning arrays (required if "Enter IDs manually" mode is chosen). |
| Result Note | A note shown only when the case status is set to "Done". |
| Additional Fields | A collection of optional fields to further describe or link the case: |
| - Description | Optional plain-text description of the case. |
| - Company ID | Related company ID (GUID). |
| - Person ID | Related person ID (GUID). |
| - Deal ID | Related deal ID (GUID). |
| - Due Date | Due date for the case. Defaults to current time if empty. |
| - Case Category | Category of the case. Options include "Activity Oriented", "Kanban", and "Ticket". |
| - Priority | Priority level of the case. Options: None, Low, Medium, High. |
| - Other Contact IDs | Additional related contact IDs (multiple GUIDs). |
| - Custom Fields (JSON) | JSON object containing custom field values keyed by field identifiers. |
| - Label IDs | Label IDs to assign to the case (multiple GUIDs). |
| - Visibility Type | Visibility setting for the case. Options: Owner, Owner Group, Owner SubGroup, All. |
Output
The node outputs an array of JSON objects representing the updated case(s). Each output item contains the full details of the case after the update, reflecting all changed properties. If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals solely with JSON data.
Dependencies
- Requires connection to Didar CRM via an API key credential configured in n8n.
- Uses Didar CRM API endpoints to perform the update operation.
- Some input options (like selecting users) rely on dynamic loading methods fetching user lists from Didar CRM.
Troubleshooting
- Missing required fields: Errors may occur if mandatory fields like Case ID, Title, Pipeline Stage ID, or Status are not provided. Ensure these are filled correctly.
- Invalid IDs: Providing incorrect or malformed GUIDs for case ID, user IDs, or related entity IDs will cause API errors. Verify IDs before use.
- Owner/User selection mismatch: If "select" mode is chosen but no user is selected, or if "manual" mode is chosen but no valid ID is entered, the update will fail.
- Status-dependent fields: The "Result Note" field is only applicable when status is "Done". Setting it otherwise might be ignored or cause validation issues.
- API authentication errors: Ensure the API key credential is valid and has sufficient permissions to update cases.
- Rate limits or network issues: Standard API call failures due to connectivity or rate limiting should be handled by retrying or checking network status.
Links and References
- Didar CRM official API documentation (for case management): [Link not provided in source]
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/
- General best practices for handling GUIDs and API authentication in integrations.