Agendor icon

Agendor

Trabalhe com dados da API do Agendor CRM
Join our community

Actions34

Overview

This node integrates with the Agendor CRM API to retrieve multiple product records. The "Get Many" operation under the "Product" resource allows users to list products or services stored in their Agendor account, supporting pagination, sorting, and search filtering.

Common scenarios where this node is beneficial include:

  • Synchronizing product catalogs from Agendor into other systems.
  • Generating reports or dashboards based on product data.
  • Automating workflows that require bulk access to product information.

For example, a user might use this node to fetch all products sorted by creation date in descending order, retrieving 50 items per page, filtered by a search term like "CRM".

Properties

Name Meaning
Options A collection of parameters to control the retrieval of products:
- Order By Field to sort results by. Options: ID, Nome (Name), Criado Em (Created At), Atualizado Em (Updated At)
- Order Direction Direction of sorting. Options: Crescente (Ascending), Decrescente (Descending)
- Page Page number to retrieve (minimum 1)
- Per Page Number of items per page (minimum 1, maximum 100)
- Search Search term to filter the results

Output

The node outputs JSON data containing an array of product objects retrieved from the Agendor API. Each product object typically includes fields such as:

  • id: Unique identifier of the product.
  • name: Name of the product or service.
  • code: Product code or SKU.
  • unit: Unit of measurement.
  • unit_price: Unit price in cents.
  • cost_price: Cost price in cents.
  • description: Detailed description.
  • category_id: Identifier for the product category.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Agendor CRM API.
  • The node uses the base URL https://api.agendor.com.br/v3.
  • Proper configuration of the API token in n8n credentials is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API token will cause authentication failures.
    • Requesting pages beyond available data may return empty results.
    • Using invalid values for sorting fields or directions may result in API errors.

  • Error Messages:

    • Authentication errors typically indicate issues with the API token; verify and update credentials.
    • Validation errors may occur if query parameters are out of allowed ranges (e.g., perPage > 100).
    • Network or connectivity errors suggest checking internet connection or API availability.

Links and References

Discussion