Actions19
- Negócio Actions
- Empresa Actions
- Pessoa Actions
- Tarefa Actions
- Produto Actions
- Usuário Actions
- Sistema Actions
Overview
This node integrates with the Agendor CRM platform to perform search operations on products. It allows users to retrieve product information by specific criteria such as product ID, product code, or to list all products. This is useful in scenarios where you want to fetch product details for further processing, reporting, or automation workflows within n8n.
Practical examples include:
- Fetching a product by its unique ID to update or verify its details.
- Searching for a product using its unique code to cross-reference inventory or pricing.
- Listing all products (with optional limits) to synchronize product catalogs or generate reports.
Properties
| Name | Meaning |
|---|---|
| Tipo de Busca | The type of search to perform. Options: "Por ID" (search by specific product ID), "Por Código" (search by product code), "Listar Todos" (list all products). |
| ID do Produto | The unique product ID in Agendor. Required if "Tipo de Busca" is "Por ID". |
| Código do Produto | The unique product code. Required if "Tipo de Busca" is "Por Código". |
| Retornar Todos | Boolean flag indicating whether to return all results when listing all products. |
| Limite | Maximum number of results to return when listing all products and "Retornar Todos" is false. Range: 1-100. |
Output
The node outputs JSON data representing the product(s) retrieved from Agendor CRM:
- When searching by ID or code, the output is a single product object with its details.
- When listing all products, the output is an array of product objects, each containing product attributes.
- The exact structure depends on the Agendor API response but typically includes fields like product ID, code, name, status, and other metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the Agendor CRM API.
- The node uses internal helper functions to make HTTP requests to Agendor endpoints.
- No additional external dependencies are required beyond the configured API authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Providing an invalid product ID or code may result in empty responses or errors.
- Requesting too many items without enabling "Retornar Todos" may limit results unexpectedly.
Error messages:
- Authentication failures: Check that the API key credential is correctly set up.
- Not found errors: Verify that the product ID or code exists in Agendor.
- Rate limiting or API errors: Consult Agendor API documentation and ensure usage complies with limits.
Links and References
- Agendor API Documentation (for detailed API endpoint info)
- n8n Documentation on Creating Custom Nodes