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 allows updating a Custom Record in Arivo CRM. It is designed to modify existing custom records by specifying the record definition, the record ID, and the fields to update. This operation is useful when you want to programmatically change details of a custom record, such as associating it with different deals, contacts, users, or teams, or updating its custom fields.
Practical examples include:
- Updating a customer’s custom record to link it to a new deal.
- Changing tags or ownership (user/team) of a custom record based on workflow conditions.
- Modifying custom fields dynamically as part of an automated data enrichment process.
Properties
| Name | Meaning |
|---|---|
| Custom Record Definition Name or ID | Select the custom record definition from a list or specify its ID via expression. This identifies the type/schema of the custom record you want to update. |
| Custom Record ID | The unique identifier of the specific custom record instance that you want to update. |
| Update Fields | A collection of fields to update on the custom record. These include: - Deal ID: ID of the associated deal. - Contact ID: ID of the associated contact. - Tags: Comma-separated tags for the record. - User Name or ID: The user responsible for the record. - Team Name or ID: The team responsible. - Custom Fields: Multiple custom fields can be set by specifying field name/ID and value pairs. |
Output
The output is a JSON object representing the updated custom record after the operation completes. It contains all relevant properties of the custom record including any updated fields.
If multiple input items are processed, the node outputs an array of JSON objects, each paired with the corresponding input item.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for Arivo CRM to authenticate requests.
- The node depends on Arivo CRM's API endpoints for custom record management.
- Load options for fields like custom record definitions, users, teams, and custom fields are dynamically fetched from Arivo CRM.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Custom Record ID will cause the update to fail.
- Incorrect or missing required fields in the update may result in errors from the API.
- Network or authentication failures if the API key is invalid or expired.
Error messages:
- Errors returned from the API typically include messages about missing permissions, invalid IDs, or validation failures.
- To resolve, verify the Custom Record Definition and Record ID exist and are accessible.
- Ensure the API key credential is valid and has sufficient permissions.
- Check that all required fields for the custom record definition are provided if applicable.
Links and References
- Arivo CRM API Documentation (hypothetical link as no direct link was provided)
- n8n Expressions Documentation
- n8n Custom Nodes Guide