Actions40
- Associação Actions
- Contato Actions
- Empresa Actions
- Negócio Actions
- Nota Actions
- Produto Actions
- Propriedade Actions
- Segmento Actions
- Tarefa Actions
- Usuário Actions
Overview
This node integrates with the Rvops platform to manage various CRM-related resources, including products. Specifically, for the "Produto" (Product) resource and the "Create a Product" operation, it allows users to create new product entries in the Rvops system. This is useful in scenarios where you want to automate product catalog management, synchronize product data from other systems, or programmatically add new products based on workflow triggers.
For example, you could use this node to automatically add a new product when a new item is added to an inventory database or when a sales team member submits a new product request form.
Properties
| Name | Meaning |
|---|---|
| Autenticação Do Cliente | Method of client authentication; currently supports "Access Token". |
| Nome Do Produto | The name of the product to be created. This is a required string input. |
| Preço Do Produto | The selling price of the product. A number with up to two decimal places, minimum 0. |
| Custo Unitário Do Produto | The unit cost or cost price of the product. A number with up to two decimal places, minimum 0. |
| Propriedades | A collection of additional product properties to set. Each property requires selecting a property name or ID and specifying its new value. Multiple properties can be added. |
Note: Other properties listed in the full JSON are related to sorting lists or other resources and are not relevant for the "Create a Product" operation.
Output
The node outputs a JSON object representing the newly created product. The structure includes:
id: The unique identifier of the created product.properties: An object containing all the properties of the product, including those set during creation.
The output is wrapped in n8n's standard execution metadata format, allowing downstream nodes to access the product data easily.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Rvops API.
- The node uses HTTP methods (POST) to communicate with the Rvops backend.
- No additional external services beyond the Rvops API are needed.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
- Authentication errors: If the API key or access token is invalid or missing, the node will fail to authenticate. Ensure the correct API key is configured.
- Validation errors: Missing required fields like "Nome Do Produto" or invalid values for price or cost may cause the API to reject the request.
- Property selection issues: When adding properties, ensure that the property names or IDs exist in the Rvops system and are correctly selected.
- API rate limits or connectivity issues: Network problems or API rate limiting might cause failures; retry or check network status.
- Error messages returned by the API are included in the output if the node is set to continue on failure, helping diagnose issues.
Links and References
- Rvops API Documentation (hypothetical link, replace with actual)
- n8n Expressions Documentation - for using expressions in property fields
- n8n Credential Setup Guide
