Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM
Join our community

Actions68

Overview

The node integrates with Arivo CRM to retrieve multiple phone records associated with a specific contact. The "Get Many" operation under the "Phone" resource fetches a list of phone entries for a given contact ID, optionally filtered by phone type and sorted by specified fields.

This node is useful in scenarios where you need to bulk retrieve all phone numbers linked to a contact, such as syncing contact details, generating reports, or validating contact information in workflows.

Practical example:

  • Fetching all phone numbers (cell, work, fax, etc.) for a customer before sending SMS notifications.
  • Retrieving a limited number of phone contacts filtered by type (e.g., only "work" phones) for display in a dashboard.

Properties

Name Meaning
Contact ID The unique identifier of the contact whose phone numbers are to be retrieved.
Return All Boolean flag indicating whether to return all matching phone records or limit the number fetched.
Limit Maximum number of phone records to return if "Return All" is false. Minimum value is 1.
Filters Collection of filters to narrow down results:
  Phone Type Filter phone numbers by type. Options: Cell, Fax, Home, Other, Work. Default is Work.
Options Additional options for sorting the results:
  Sort Field Field to sort the results by. Options: Created At, Updated At, Number. Default is Created At.
  Sort Order Sort direction. Options: Ascending, Descending. Default is Descending.

Output

The output is an array of JSON objects, each representing a phone record associated with the specified contact. Each object contains details about a phone entry, such as its type, number, creation date, update date, and any other metadata provided by Arivo CRM.

The output items are paired with their corresponding input item index to maintain traceability in workflows.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with Arivo CRM.
  • The node depends on the Arivo CRM API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will result in errors or empty results.
    • API authentication failures due to incorrect or expired credentials.
    • Network connectivity issues preventing access to Arivo CRM API.
    • Requesting too many records without enabling "Return All" may cause partial data retrieval.

  • Error messages and resolutions:

    • "Contact ID is required": Ensure the Contact ID property is set and valid.
    • "Authentication failed": Verify that the API key credential is correctly configured and has necessary permissions.
    • "Rate limit exceeded": Reduce request frequency or enable pagination using "Return All" and "Limit" properties.
    • "Resource not found": Confirm the contact exists in Arivo CRM and the ID is correct.

Links and References

Discussion