Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Overview

The node integrates with Arivo CRM to retrieve multiple company records based on specified filters and options. It is designed to fetch a list of companies, optionally filtered by various criteria such as location, contact details, tags, or associated team/user. Users can choose to return all matching companies or limit the number of results.

This operation is beneficial when you need to bulk retrieve company data for reporting, synchronization with other systems, or batch processing workflows. For example, you might use it to get all companies in a specific city or all companies tagged with a certain label.

Properties

Name Meaning
Return All Whether to return all matching company records or only up to a specified limit.
Limit Maximum number of company records to return (used if "Return All" is false).
Filters Criteria to filter the companies by various fields:
- City Filter companies by their city.
- CNPJ Filter by Brazilian company taxpayer registration number.
- Country Filter companies by country.
- District Filter companies by district.
- Email Filter companies by email address.
- Name Filter companies by company name.
- Phone Filter companies by phone number.
- State Filter companies by state or province.
- Tags Filter companies by tags (comma-separated list).
- Team Name or ID Filter companies by associated team (selectable from available teams).
- User Name or ID Filter companies by associated user (selectable from available users).
- Zip Code Filter companies by ZIP code.
Options Additional options for sorting the results:
- Sort By Field to sort the results by: Created At, Email, Name, or Updated At.
- Sort Order Order to sort results: Ascending or Descending.

Output

The output is an array of JSON objects, each representing a company record retrieved from Arivo CRM. Each object contains the company's data fields as returned by the API, including but not limited to identifiers, contact information, address details, tags, and metadata.

The output items are paired with the input item index they correspond to, allowing traceability in workflows.

No binary data is output 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 company data retrieval.
  • The node uses internal methods to load selectable options for filtering by team and user.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using invalid filter values (e.g., non-existent team or user IDs) may result in empty results or errors.
    • Requesting too many records without enabling pagination or "Return All" may hit API limits.
  • Error Messages:

    • Authentication errors indicate issues with the provided API key; verify and update credentials.
    • Validation errors on filters suggest incorrect input formats; ensure filters match expected types.
    • Rate limit errors from the API require implementing delays or reducing request frequency.

Links and References

Discussion