Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The "Person - Get Many" operation in this node retrieves multiple person records from the Arivo CRM system. It allows users to fetch a list of contacts filtered by various criteria such as city, company ID, email, tags, and more. Users can choose to return all matching results or limit the number of returned records. Additionally, the results can be sorted by fields like creation date, email, name, or update date in ascending or descending order.

This operation is beneficial when you need to bulk retrieve contact information for marketing campaigns, reporting, data synchronization, or any scenario where you want to process or analyze multiple person records at once.

Practical examples:

  • Fetching all persons located in a specific city or country.
  • Retrieving up to 100 contacts tagged with a particular label.
  • Getting a sorted list of recently updated contacts for follow-up.

Properties

Name Meaning
Return All Whether to return all matching person records or only up to a specified limit.
Limit The maximum number of person records to return if "Return All" is set to false. Minimum value is 1.
Filters Collection of filters to narrow down the search results. Includes:
• City
• Company ID
• Country
• CPF (Brazilian individual taxpayer registration)
• District
• Email
• Name
• Phone
• State/Province
• Tags (comma-separated)
• Team Name or ID (selectable options)
• User Name or ID (selectable options)
• Zip Code
Options Additional options for sorting the results:
• Sort By: Created At, Email, Name, Updated At
• Sort Order: Ascending or Descending

Output

The output is an array of JSON objects, each representing a person record retrieved from Arivo CRM. Each object contains the person's details according to the filters and options applied.

The structure typically includes fields such as:

  • Person identifiers
  • Contact information (email, phone)
  • Address details (city, state, country, zip code)
  • Associated company or team IDs
  • Tags and other metadata

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Arivo CRM API.
  • The node depends on the Arivo CRM service being accessible and properly configured.
  • For filtering by team or user, the node loads selectable options dynamically via methods that fetch available teams and users from Arivo CRM.

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 "Return All" might truncate results unexpectedly.

  • Error messages:

    • Authentication errors: Verify that the API key credential is correctly set up.
    • Validation errors on filters: Check that filter values conform to expected formats and exist in the CRM.
    • Rate limiting or network errors: Ensure stable internet connection and respect API usage limits.

Links and References

Discussion