Arivo CRM icon

Arivo CRM

Create and edit data in Arivo CRM

Actions68

Overview

The "Get Many" operation for the "Custom Record" resource in this node allows users to retrieve multiple custom records from Arivo CRM based on specified criteria. This operation is useful when you want to fetch a list of custom records filtered by various attributes such as associated contact, deal, tags, user, or team. It supports pagination control by allowing either fetching all records or limiting the number of results returned.

Practical examples include:

  • Retrieving all custom records linked to a specific contact or deal.
  • Fetching custom records tagged with certain keywords.
  • Getting custom records assigned to a particular user or team.
  • Sorting the results by creation or update date in ascending or descending order.

This operation helps automate workflows that require bulk data retrieval and processing of custom records within Arivo CRM.

Properties

Name Meaning
Custom Record Definition Name or ID Select the custom record definition from a list or specify its ID via an expression. This identifies which type of custom records to retrieve.
Return All Boolean flag indicating whether to return all matching results (true) or limit the output to a specified number (false).
Limit When "Return All" is false, this sets the maximum number of custom records to return (minimum 1).
Filters Collection of optional filters to narrow down the results:
- Contact ID: Filter by the ID of the associated contact.
- Deal ID: Filter by the ID of the associated deal.
- Tags: Comma-separated tags to filter by.
- User Name or ID: Filter by the responsible user.
- Team Name or ID: Filter by the responsible team.
Options Additional options for sorting the results:
- Sort Field: Choose to sort by "Created At" or "Updated At".
- Sort Order: Choose ascending or descending order.

Output

The output is an array of JSON objects, each representing a custom record retrieved from Arivo CRM. Each object contains the fields and values of a single custom record according to the selected custom record definition.

  • The output items are paired with their input items to maintain traceability.
  • No binary data is produced by this operation.

Example output structure (simplified):

[
  {
    "json": {
      "id": "123",
      "name": "Sample Custom Record",
      "contact_id": "456",
      "deal_id": "789",
      "tags": ["tag1", "tag2"],
      "user_id": "user_1",
      "team_id": "team_1",
      "created_at": "2023-01-01T12:00:00Z",
      "updated_at": "2023-01-02T12:00:00Z",
      ...
    },
    "pairedItem": {
      "item": 0
    }
  },
  ...
]

Dependencies

  • Requires connection to Arivo CRM via an API key credential configured in n8n.
  • The node depends on Arivo CRM's API endpoints for custom records.
  • Load options for dropdowns (e.g., custom record definitions, users, teams) are dynamically fetched from Arivo CRM.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Specifying an invalid custom record definition ID or name may result in no data or errors.
    • Using filters with incorrect IDs or formats can lead to empty results.
    • Exceeding API rate limits may cause request failures.

  • Error messages:

    • Authentication errors: Verify the API key credential is correctly set up.
    • Not found errors: Check that the custom record definition exists and the IDs used in filters are valid.
    • Validation errors: Ensure numeric limits and boolean flags are properly configured.

  • To resolve issues, verify credentials, confirm filter values, and consult Arivo CRM API documentation for limits and constraints.

Links and References

Discussion