Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node operation updates an existing activity record in Didar CRM by its unique identifier. It allows users to modify various details of the activity such as title, type, owner, status (done or not), notes, tags, related entities (deals, cases, contacts), recurrence settings, and other metadata.
Common scenarios where this node is beneficial include:
- Updating the status or details of a scheduled task or event.
- Changing ownership or reassigning activities to different users.
- Adding notes or results after completing an activity.
- Managing recurring activities with specific recurrence patterns.
- Soft-deleting or pinning important activities for visibility.
Practical example: After a sales call activity is completed, you can update the activity to mark it as done, add outcome notes, and tag it with relevant labels for reporting.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the activity to update (required). |
| Title | The new title of the activity (required). |
| Activity Type Input Mode | Choose how to specify the activity type: either select from a predefined list or enter the ID manually. |
| Activity Type | Select the activity type from a list (required if "select" mode is chosen). |
| Activity Type ID | Enter the activity type ID manually (required if "manual" mode is chosen). |
| Owner Input Mode | Choose how to specify the owner user: either select from a list or enter the ID manually. |
| Owner | Select the owner user from a list (required if "select" mode is chosen). |
| Owner ID | Enter the owner user ID manually (required if "manual" mode is chosen). |
| Is Done | Boolean flag to mark the activity as completed. |
| Additional Fields | A collection of optional fields to further customize the activity update: |
| - Note | Text note or description of the activity. |
| - Result Note | Notes about the result or outcome of the activity. |
| - Tags | List of tag IDs associated with the activity. Only sent if "Result Note" is provided. Accepts multiple values via CSV, JSON array, or new lines. |
| - Is Deleted | Boolean flag to soft-delete the activity. |
| - Is Pinned | Boolean flag to pin the activity for prominence. |
| - Due Date | Planned due date/time in ISO format. |
| - Duration | Duration of the activity in minutes; only sent if greater than zero. |
| - Done Date | Completion date/time in ISO format. |
| - Deal ID | Related deal ID; use zero GUID if none. |
| - Case ID | Related case ID; use zero GUID if none. |
| - Contact IDs | List of related contact IDs. Accepts multiple values. |
| - Creator ID | Creator user ID; defaults to zero GUID if unspecified. |
| - Recurrence Type | Recurrence pattern of the activity; options include OneTime, Hourly, Daily, Weekly, Monthly, Yearly, or empty for no recurrence. |
| - Recurrence Data | Positive integer data related to recurrence; only sent if greater than zero. |
| - Recurrence End Date | End date/time for recurrence in ISO format. |
Output
The node outputs an array of JSON objects representing the updated activity records. Each output item contains the updated activity data as returned by the Didar CRM API, including all fields that were modified or retrieved during the update operation.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the activity, but this operation focuses on JSON data updates only.
Dependencies
- Requires an active connection to Didar CRM via an API key credential configured in n8n.
- The node depends on internal methods to load selectable options for activity types and users.
- Proper permissions in Didar CRM are necessary to update activities.
Troubleshooting
- Missing Required Fields: Errors may occur if mandatory fields like "Id" or "Title" are missing. Ensure these are provided.
- Invalid IDs: Providing invalid or non-existent activity, user, or type IDs will cause update failures. Verify IDs before running.
- Permission Denied: Insufficient API permissions or expired credentials can lead to authorization errors.
- Incorrect Data Formats: Date/time fields must be in ISO format; duration must be a non-negative number.
- Tags Without Result Note: Tags are only sent if a "Result Note" is provided; otherwise, they are ignored.
- Soft Delete Conflicts: Setting "Is Deleted" to true marks the activity as deleted without removing it permanently; ensure this matches your intent.
To resolve errors, verify input parameters, check API credentials, and consult Didar CRM API documentation for valid field values.
Links and References
- Didar CRM API Documentation (replace with actual URL)
- ISO 8601 Date Format Reference
- n8n Documentation on Creating Custom Nodes