Actions68
- Email Actions
- File Actions
- Note Actions
- Product Category Actions
- Task Actions
- Address Actions
- Company Actions
- Custom Record Actions
- Deal Actions
- Deal Item Actions
- Person Actions
- Phone Actions
- Product Actions
Overview
The node integrates with Arivo CRM to manage custom records. Specifically, the "Get" operation for the "Custom Record" resource retrieves a single custom record by its ID from a specified custom record definition.
This node is useful when you want to fetch detailed information about a specific custom record stored in Arivo CRM, such as retrieving customer-specific data, custom forms, or any user-defined entity that has been set up in the CRM.
Practical example:
You have a custom record definition named "Event Registrations" in Arivo CRM, and you want to retrieve the details of a particular registration by its unique ID to process it further in your workflow (e.g., send a confirmation email or update another system).
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 record you want to access. |
| Custom Record ID | The unique identifier of the custom record you want to retrieve. |
Output
The output is a JSON object representing the retrieved custom record's data fields as stored in Arivo CRM. It contains all the properties and values defined for that custom record instance.
- The
jsonoutput field includes the full details of the custom record. - No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to Arivo CRM via an API key credential configured in n8n.
- The node depends on the Arivo CRM API being accessible and the user having permissions to read custom records.
- The property "Custom Record Definition Name or ID" uses a dynamic options loader to fetch available custom record definitions from Arivo CRM.
Troubleshooting
Common issues:
- Invalid or missing Custom Record ID: The node will fail if the provided custom record ID does not exist or is malformed.
- Incorrect Custom Record Definition: Selecting a wrong or non-existent custom record definition may cause errors or empty results.
- API authentication errors: If the API key credential is invalid or expired, the node will not be able to connect.
- Network connectivity problems can prevent the node from reaching Arivo CRM.
Error messages and resolutions:
"Record not found": Verify the Custom Record ID is correct and exists under the selected definition."Authentication failed": Check the API key credential configuration and renew if necessary."Permission denied": Ensure the API user has rights to read custom records."Invalid parameter": Confirm that the Custom Record Definition and ID are correctly specified.
Links and References
- Arivo CRM Documentation (general reference for API and custom records)
- n8n Expressions Documentation (for using expressions in property fields)