Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node integrates with the Agendor CRM API to update product information. It allows users to modify details of an existing product by specifying its unique Product ID and any fields they want to change. This is useful in scenarios where product data such as name, SKU code, pricing, description, or category needs to be kept current within the CRM system.
Practical examples include:
- Updating the price of a product after a cost change.
- Correcting or adding a detailed description for better clarity.
- Changing the unit of measure or SKU code to align with inventory systems.
- Assigning or updating the product’s category for improved organization.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to update (required). |
| Name | The product's name. Leave empty if you do not want to change it. |
| Code | The product's SKU code. |
| Description | A detailed description of the product. |
| Unit | The unit of measurement (e.g., unit, kg, liter). |
| Unit Price | The unit price of the product in cents (e.g., 1000 = R$10.00). |
| Cost Price | The cost price of the product in cents. |
| Category ID | Optional ID of the product category. |
| Additional Fields | A collection of optional extra fields that can be added depending on context (not typically used for products). |
Output
The node outputs JSON data representing the updated product object returned from the Agendor API. This JSON includes all the product properties after the update, reflecting the new values set by the user. There is no binary data output.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Agendor CRM API.
- The base URL for API requests is
https://api.agendor.com.br/v3. - The node sends HTTP PUT requests to
/products/{productId}endpoint with the updated product data.
Troubleshooting
- Missing Product ID: The update operation requires a valid Product ID. If omitted or incorrect, the API will return an error indicating the product was not found.
- Invalid Field Values: Providing invalid data types or formats (e.g., negative prices) may cause the API to reject the request.
- Authentication Errors: Ensure the API token credential is correctly set up and has sufficient permissions.
- Empty Update Fields: If all update fields are left empty, the API might ignore the request or return the original product unchanged.
- API Rate Limits: Frequent updates may hit API rate limits; handle errors accordingly.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for general usage of custom nodes and credentials)