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 integrates with Arivo CRM to create a new Task record. It allows users to specify the task's name and various optional details such as type, due date, completion status, related contacts or deals, responsible user or team, comments, and tags. This node is useful for automating task creation workflows in sales, customer support, or project management scenarios where tasks need to be tracked and assigned within Arivo CRM.
Practical examples:
- Automatically creating follow-up call tasks after a new lead is added.
- Scheduling reminder tasks with due dates for account managers.
- Creating tasks linked to specific deals or contacts to track progress.
Properties
| Name | Meaning |
|---|---|
| Name | The title or name of the task (e.g., "Follow up call with client"). This is a required field. |
| Additional Fields | A collection of optional fields to further define the task: |
| - Task Type Name or ID | The category or type of the task. Choose from a list loaded dynamically or specify an ID via expression. |
| - Due Type | Whether the task has a due date ("With Date") or no due date ("No Date"). Options: "With Date", "No Date". |
| - Due Date | The starting date and time when the task is due. Only shown if "Due Type" is "With Date". |
| - Due Date End | The ending date and time for the task, must be after the Due Date. Only shown if "Due Type" is "With Date". |
| - Done | Boolean flag indicating whether the task is marked as completed. |
| - Comment | Additional comments or notes about the task. |
| - Contact ID | Numeric ID of the contact or company associated with this task. |
| - Deal ID | Numeric ID of the deal or opportunity related to this task. |
| - User Name or ID | The user responsible for the task. Choose from a dynamically loaded list or specify an ID via expression. |
| - Team Name or ID | The team responsible for the task. Choose from a dynamically loaded list or specify an ID via expression. |
| - Tags | Comma-separated list of tags to categorize or label the task. |
Output
The node outputs JSON data representing the created task object as returned by the Arivo CRM API. This typically includes all properties of the newly created task such as its unique ID, name, type, due dates, status, related entities (contact, deal), assigned user/team, comments, and tags.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the task, but this node focuses on JSON task data only.
Dependencies
- Requires an active connection to Arivo CRM via an API key credential configured in n8n.
- The node depends on dynamic loading methods to fetch options for task types, users, and teams from Arivo CRM.
- Proper permissions in Arivo CRM are needed to create tasks and access related entities like contacts, deals, users, and teams.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Specifying invalid IDs for task type, user, team, contact, or deal may result in errors or failed task creation.
- Setting a due date end that is before the due date will likely cause validation errors.
- Network connectivity problems can prevent communication with Arivo CRM.
Error messages:
- Authentication errors: Verify API key credential and permissions.
- Validation errors: Check that required fields are provided and that date ranges are valid.
- Not found errors: Ensure referenced IDs (e.g., contact_id, deal_id) exist in Arivo CRM.
Resolution tips:
- Use the dynamic option loaders to select valid values rather than manually entering IDs.
- Double-check date/time formats and logical ordering.
- Enable "Continue On Fail" in the node settings to handle individual item errors gracefully during batch operations.
Links and References
- Arivo CRM Documentation (general reference for API and task management)
- n8n Expressions Documentation (for using expressions in property fields)
- n8n Credential Setup (for configuring API keys)