Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node enables creating a new activity record in Didar CRM. Activities represent tasks, events, or actions related to deals, cases, contacts, or other CRM entities. The node is useful for automating task management workflows, logging interactions, scheduling follow-ups, or tracking progress on various CRM items.
Typical use cases include:
- Automatically creating a follow-up call or meeting activity after a deal update.
- Logging completed tasks with notes and results.
- Scheduling recurring activities such as daily check-ins or weekly reviews.
- Associating activities with specific owners, deals, cases, or contacts.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the activity (required). |
| Activity Type Input Mode | Choose how to specify the activity type: either select from a list or enter the ID manually. |
| Activity Type | Select the activity type from a dynamically loaded 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 dynamically loaded 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 provide more details about the activity: |
| - 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. Accepts multiple entries in CSV, JSON array, or newline formats. Sent only if "Result Note" is provided. |
| - Is Deleted | Soft-delete flag for the activity. |
| - Is Pinned | Flag to pin the activity. |
| - Due Date | Planned due date/time in ISO format. |
| - Duration | Duration of the activity in minutes (only sent if greater than 0). |
| - Done Date | Completion date/time in ISO format. |
| - Deal ID | Related deal ID (GUID). Use zero-guid if none. |
| - Case ID | Related case ID (GUID). Use zero-guid if none. |
| - Contact IDs | List of related contact IDs. Accepts multiple values. |
| - Creator ID | Creator user ID (GUID). |
| - Recurrence Type | Recurrence pattern for the activity. Options include OneTime, Hourly, Daily, Weekly, Monthly, Yearly, or empty for non-recurring. |
| - Recurrence Data | Positive integer specifying recurrence interval (only sent if > 0). |
| - Recurrence End Date | End date/time for recurrence in ISO format. |
Output
The node outputs an array of JSON objects representing the created activity records. Each object contains the details of the newly created activity, including its unique identifier and all submitted properties.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the activity, but this node focuses on JSON data only.
Dependencies
- Requires an API key credential for authenticating with Didar CRM's API.
- Uses dynamic option loading methods to fetch lists of users and activity types from Didar CRM.
- The node depends on proper configuration of the Didar CRM API credentials within n8n.
Troubleshooting
- Missing required fields: Ensure that mandatory fields like "Title" and either "Activity Type" or "Activity Type ID" are provided depending on the input mode.
- Invalid IDs: Manually entered IDs for activity type, owner, deal, case, or contacts must be valid GUIDs recognized by Didar CRM.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Incorrect recurrence settings: If using recurrence, ensure that "Recurrence Data" is a positive integer and "Recurrence End Date" is a valid ISO date string.
- Tags field usage: Tags are sent only if "Result Note" is provided; otherwise, tags will be ignored.
- Soft-delete flag confusion: Setting "Is Deleted" to true marks the activity as deleted without removing it permanently; use carefully.
Links and References
- Didar CRM API Documentation (replace with actual URL)
- n8n Custom Node Development Guide
- ISO 8601 Date Format Reference