Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The node integrates with Arivo CRM to manage tasks. Specifically, the Task - Get Many operation retrieves multiple task records from the CRM based on user-defined filters and options. This is useful for scenarios where you want to fetch a list of tasks matching certain criteria, such as tasks assigned to a specific user, tasks related to a particular deal, or tasks filtered by completion status.

Practical examples include:

  • Retrieving all incomplete tasks assigned to a team member.
  • Fetching tasks linked to a specific contact or deal.
  • Getting tasks sorted by due date or creation date for reporting or automation purposes.

Properties

Name Meaning
Limit Maximum number of task results to return (minimum 1).
Filters Collection of filters to narrow down the tasks returned:
- Contact ID: Filter tasks by associated contact ID (number).
- Creator ID: Filter tasks by creator user ID (number).
- Deal ID: Filter tasks by associated deal ID (number).
- Done: Filter by completion status; options are "True" or "False".
- Name: Filter tasks by partial match on task name (string).
- Tags: Filter tasks by tags, comma-separated string.
- Task Type Name or ID: Filter by task type, selectable from loaded task types.
- Team Name or ID: Filter by team, selectable from loaded teams.
- User Name or ID: Filter by user, selectable from loaded users.
Options Additional options for sorting the results:
- Sort By: Field to sort results by; options include Completed At, Created At, Due Date, Updated At.
- Sort Order: Order to sort results; options are Ascending or Descending.

Output

The output is an array of JSON objects, each representing a task record retrieved from Arivo CRM. Each object contains the full details of a task matching the specified filters and options.

  • The json field holds the task data.
  • The output pairs each result with the corresponding input item index (pairedItem), preserving context in workflows.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for Arivo CRM configured in n8n.
  • The node depends on Arivo CRM's API endpoints for fetching task data.
  • Load options for filters like task types, teams, and users are dynamically fetched via helper methods integrated into the node.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using invalid filter values (e.g., non-existent IDs) may result in empty results or errors.
    • Exceeding API rate limits could cause request failures.

  • Error messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Validation errors on filters suggest incorrect parameter formats; ensure numeric fields receive numbers and option fields use valid selections.
    • Network or timeout errors may require checking connectivity or retrying later.

Links and References

Discussion