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 creating a new Custom Record in Arivo CRM. A Custom Record is a user-defined data structure that can represent any entity or object tailored to specific business needs, beyond standard CRM entities like contacts or deals.
This operation is useful when you want to store and manage custom data types within Arivo CRM, such as specialized forms, unique asset tracking, or any bespoke record type your organization requires.
Example use cases:
- Creating a custom record for tracking equipment maintenance logs.
- Adding a custom record for event registrations with fields specific to the event.
- Storing additional metadata related to deals or contacts that do not fit into default CRM fields.
Properties
| Name | Meaning |
|---|---|
| Custom Record Definition Name or ID | The identifier or name of the custom record definition that defines the schema/structure of the record you want to create. You can select from a list or specify an ID dynamically using expressions. This determines what fields are available. |
| Additional Fields | A collection of optional fields to set on the custom record. These include: |
| Deal ID | The ID of the deal associated with this custom record. |
| Contact ID | The ID of the contact associated with this custom record. |
| Tags | Comma-separated tags to categorize or label the custom record. |
| User Name or ID | The user responsible for this custom record. Select from a list or specify an ID dynamically. |
| Team Name or ID | The team responsible for this custom record. Select from a list or specify an ID dynamically. |
| Custom Fields | One or more custom fields specific to the selected custom record definition. Each custom field requires specifying the field name or ID and the value to assign. |
Output
The output JSON contains the newly created custom record's data as returned by the Arivo CRM API. This typically includes:
- The unique ID of the created custom record.
- All fields and values set on the record, including system-generated fields.
- Metadata such as creation timestamps or status if provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to Arivo CRM via an API key credential configured in n8n.
- The node depends on Arivo CRM's API endpoints for managing custom records.
- Dynamic options (e.g., for selecting custom record definitions, users, teams, and custom fields) are loaded via internal methods querying Arivo CRM.
Troubleshooting
- Invalid Custom Record Definition: If the specified custom record definition name or ID does not exist or is incorrect, the API will return an error. Verify the definition exists and is accessible.
- Missing Required Fields: Some custom record definitions may require mandatory fields. Ensure all required fields are provided in the "Additional Fields" or "Custom Fields" collections.
- Authentication Errors: If the API key credential is missing, invalid, or expired, authentication errors will occur. Check the credential configuration.
- Invalid Field Values: Providing values incompatible with the expected field type (e.g., string instead of number) may cause errors. Validate field types before sending.
- API Rate Limits: Excessive requests might be throttled by Arivo CRM. Implement retry logic or reduce request frequency if needed.
Links and References
- Arivo CRM Documentation (general reference for API and custom records)
- n8n Expressions Documentation (for dynamic parameter usage)
- Arivo CRM Custom Records Guide (if available, for detailed custom record setup)