Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The node integrates with Arivo CRM to retrieve multiple Note records based on specified filters and sorting options. It is designed to fetch a list of notes associated with contacts, deals, tasks, users, or teams within the CRM system.

Common scenarios where this node is beneficial include:

  • Extracting recent notes linked to specific contacts or deals for reporting or analysis.
  • Synchronizing notes data from Arivo CRM into other systems or databases.
  • Filtering notes by user or team to monitor activity or performance.

For example, a user might configure the node to get up to 50 notes related to a particular deal, sorted by creation date in descending order, to review recent communications or updates.

Properties

Name Meaning
Limit Max number of note results to return (minimum 1, default 50).
Filters Collection of optional filters to narrow down the notes:
- Contact ID: Filter notes by a specific contact's ID.
- Deal ID: Filter notes by a specific deal's ID.
- Task ID: Filter notes by a specific task's ID.
- User Name or ID: Filter notes created by a specific user (selectable from user options).
- Team Name or ID: Filter notes associated with a specific team (selectable from team options).
Options Additional options for result sorting:
- Sort By: Choose field to sort results by — either "Created At" or "Updated At" (default "Updated At").
- Sort Order: Choose sorting order — "Ascending" or "Descending" (default "Descending").

Output

The output is an array of JSON objects, each representing a Note record retrieved from Arivo CRM. Each item corresponds to one note and includes all relevant fields as provided by the CRM API.

The structure typically contains identifiers, content, timestamps (created and updated), and associations to contacts, deals, tasks, users, or teams depending on the note's context.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to Arivo CRM via an API key credential configured in n8n.
  • The node depends on Arivo CRM's API endpoints for Notes.
  • To populate user and team filter options, the node uses internal methods to load these dynamically from Arivo CRM.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid IDs in filters (e.g., non-existent contact or deal IDs) may result in empty results or errors.
    • Exceeding API rate limits can cause request failures.

  • Error Messages:

    • Authentication errors indicate issues with the API key; verify and reconfigure credentials.
    • "Not Found" errors suggest that filtered entities (contact, deal, task, user, or team) do not exist or are inaccessible.
    • Network or timeout errors require checking connectivity and retrying.

  • Resolution Tips:

    • Ensure all filter IDs correspond to valid entities in Arivo CRM.
    • Confirm API credentials are correctly set and have sufficient permissions.
    • Use smaller limits if large data sets cause timeouts.

Links and References

Discussion