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
This node integrates with Arivo CRM to create or update product categories. It allows users to either add a new product category or update an existing one by matching on a specified field (either the category name or an external code). This is useful for maintaining an up-to-date and organized product catalog within Arivo CRM, especially when syncing data from other systems or automating category management.
Practical examples:
- Automatically creating new product categories when importing products from an external inventory system.
- Updating existing product categories' external codes or names based on changes in a master database.
- Ensuring that product categories are consistent across multiple platforms by matching and updating them via this node.
Properties
| Name | Meaning |
|---|---|
| Category Name | The name of the product category to create or update. |
| Field to Match On | The field used to find existing categories to update. Options: "Name" or "Code". |
| Additional Fields | Optional extra fields to set on the category. Currently supports: |
| - Code: External code for system identification |
Output
The node outputs JSON objects representing the created or updated product category. Each output item corresponds to one processed input item and contains the details of the product category as returned by Arivo CRM after the operation.
If the node encounters errors during processing and is configured to continue on failure, it outputs an error object with an error property describing the issue.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with Arivo CRM.
- Needs proper configuration of the Arivo CRM API credentials within n8n.
- Network access to Arivo CRM's API endpoints.
Troubleshooting
Common issues:
- Mismatched or missing API credentials will cause authentication failures.
- Using a match field that does not correspond to any existing category may result in unintended creation instead of update.
- Providing invalid or incomplete category data can lead to API validation errors.
Error messages:
- Errors returned from Arivo CRM API will be surfaced with their message in the output if "Continue on Fail" is enabled.
- Authentication errors typically indicate invalid or expired API keys; recheck and update credentials.
- Validation errors usually mean required fields are missing or have invalid values; verify input properties.
Links and References
- Arivo CRM API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes