Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The node integrates with Arivo CRM to retrieve multiple deal records based on specified filters and options. The "Get Many" operation for the "Deal" resource allows users to fetch a list of deals, optionally filtered by criteria such as company, contact, pipeline stage, status, tags, team, temperature, or user. It supports pagination control by either returning all results or limiting the number of returned deals.

This node is beneficial in scenarios where you want to analyze, report, or synchronize multiple deals from Arivo CRM into other systems or workflows. For example, you could use it to:

  • Retrieve all open deals in a specific sales pipeline to generate a sales forecast.
  • Fetch recently updated deals limited to 50 entries for dashboard display.
  • Filter deals by tags or assigned teams to segment data for targeted marketing campaigns.

Properties

Name Meaning
Return All Whether to return all matching deal records or only up to a specified limit.
Limit Maximum number of deal records to return when "Return All" is false. Minimum value is 1.
Filters Collection of optional filters to narrow down the deals retrieved:
- Company ID: Filter deals associated with a specific company.
- Contact ID: Filter deals linked to a particular contact.
- Name: Filter by deal name.
- Pipeline Name or ID: Filter deals within a specific sales pipeline.
- Pipeline Step Name or ID: Filter deals at a specific step/stage in the pipeline.
- Status: Filter deals by their status (Open, Won, Lost).
- Tags: Filter deals by comma-separated tags.
- Team Name or ID: Filter deals assigned to a specific team.
- Temperature: Filter deals by temperature classification (Cold, Warm, Hot).
- User Name or ID: Filter deals assigned to a specific user.
Options Additional options for sorting the results:
- Sort By: Field to sort the deals by (Created At, Estimated Close Date, Name, Opened At, Updated At, Value).
- Sort Order: Ascending or Descending order for sorting.

Output

The output is an array of JSON objects, each representing a deal record retrieved from Arivo CRM. Each object contains the full details of a deal according to the fields defined in Arivo CRM's deal schema. The structure typically includes identifiers, names, statuses, pipeline information, monetary values, dates, tags, and related entity references.

If multiple deals are returned, each is paired with the corresponding input item index for traceability.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with Arivo CRM.
  • The node depends on Arivo CRM's REST API endpoints for deals.
  • Load options for filters like pipelines, pipeline steps, teams, and users are dynamically fetched via internal methods that query Arivo CRM.
  • Proper configuration of the API credential in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Authentication failures due to invalid or missing API credentials.
    • No results returned if filters are too restrictive or incorrect IDs/names are provided.
    • Rate limiting or API quota exceeded errors from Arivo CRM.
    • Sorting or filtering options not applied correctly if dependent load options fail.

  • Error Messages:

    • Errors containing messages about authentication usually indicate issues with the API key setup.
    • Errors mentioning invalid filter parameters suggest checking the filter values for correctness.
    • Network or timeout errors may require retrying or checking connectivity.

  • Resolutions:

    • Verify and update the API key credential in n8n settings.
    • Double-check filter values against Arivo CRM data (e.g., valid pipeline IDs).
    • Reduce request frequency or implement error handling with retries.
    • Use the "Return All" option carefully to avoid large data loads causing timeouts.

Links and References

Discussion