Actions68
- Email Actions
- File Actions
- Note Actions
- Product Category Actions
- Task Actions
- Address Actions
- Company Actions
- Custom Record Actions
- Deal Actions
- Deal Item Actions
- Person Actions
- Phone Actions
- Product Actions
Overview
The node allows updating an existing task in Arivo CRM. It is useful for workflows that need to modify task details such as changing the task name, type, due date, completion status, or associating it with different contacts, deals, users, or teams. For example, you could automate marking a task as done when a related deal is closed, or update the due date based on external calendar events.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update (required). |
| Update Fields | A collection of fields to update on the task: |
| - Name | New name/title of the task. |
| - Task Type Name or ID | The type/category of the task, selectable from a list or specified by ID. |
| - Due Type | Whether the task has a due date ("With Date") or no due date ("No Date"). |
| - Due Date | The date and time when the task is due (shown only if Due Type is "With Date"). |
| - Due Date End | The end date and time for the task, must be after the Due Date (shown only if Due Type is "With Date"). |
| - Done | Boolean flag indicating if the task is marked as completed. |
| - Comment | A comment or note about the task. |
| - Contact ID | ID of the contact or company related to this task. |
| - Deal ID | ID of the deal or opportunity related to this task. |
| - User Name or ID | The user responsible for this task, selectable from a list or specified by ID. |
| - Team Name or ID | The team responsible for this task, selectable from a list or specified by ID. |
| - Tags | Comma-separated list of tags associated with the task. |
Output
The node outputs JSON data representing the updated task object returned from Arivo CRM. This includes all the task's properties after the update operation, such as its ID, name, type, due dates, completion status, related entities, comments, and tags.
There is no binary data output.
Dependencies
- Requires an API key credential for Arivo CRM configured in n8n.
- Uses Arivo CRM's REST API endpoints to perform the update operation.
- Some input options (e.g., Task Type, User, Team) are dynamically loaded via helper methods that fetch available options from Arivo CRM.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Task ID will cause the update to fail.
- Setting a Due Date End earlier than the Due Date will likely result in an error.
- Omitting required authentication credentials will prevent API calls.
- Using incorrect IDs or names for related entities (contact, deal, user, team) may cause errors or unexpected behavior.
Error messages:
- Errors from the Arivo CRM API typically include messages about invalid IDs, missing permissions, or validation failures.
- Network or authentication errors indicate problems with the API key or connectivity.
Resolutions:
- Verify the Task ID exists before attempting update.
- Ensure Due Date End is after Due Date if both are set.
- Confirm API credentials are correctly configured and have necessary permissions.
- Use the dynamic option loaders to select valid related entity IDs.
Links and References
- Arivo CRM API Documentation (example placeholder, replace with actual URL if known)
- n8n Expressions Documentation — for using expressions in property values.