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 manage product data. Specifically, the "Get" operation for the "Product" resource allows users to retrieve detailed information about a specific product by its ID. This is useful in scenarios where you want to fetch product details such as name, code, pricing, description, and category from your CRM system within an automated workflow.
Practical examples include:
- Automatically retrieving product details when processing orders or quotes.
- Syncing product information between Agendor CRM and other systems.
- Using product data to trigger further automation steps based on product attributes.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to retrieve. This is required to specify which product's details should be fetched. |
Output
The node outputs JSON data representing the product object retrieved from the Agendor API. This typically includes fields such as product name, code (SKU), unit, unit price, cost price, description, and category ID, among others.
If the product exists, the output JSON will contain all available details of that product as returned by the API.
The node does not output binary data.
Dependencies
- Requires an API authentication token credential for the Agendor CRM API.
- The base URL used for requests is
https://api.agendor.com.br/v3. - The node sends HTTP GET requests to the endpoint
/products/{productId}, where{productId}is replaced by the provided Product ID.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Product ID will likely result in an error or empty response.
- Missing or incorrect API authentication token will cause authorization errors.
- Network connectivity issues can prevent successful API calls.
Common error messages:
- Unauthorized or 401 errors indicate missing or invalid API credentials. Ensure the API token is correctly configured.
- 404 Not Found errors mean the specified Product ID does not exist in the CRM.
- Rate limiting or 429 errors may occur if too many requests are made in a short time; consider adding delays or retries.
Links and References
- Agendor API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general guidance on using custom nodes and credentials)