Agendor icon

Agendor

Trabalhe com dados da API do Agendor CRM

Overview

This node integrates with the Agendor CRM API to manage user data. Specifically, the User - Get Many operation retrieves multiple user records from the Agendor system. It supports filtering, sorting, and pagination of user lists, making it useful for workflows that need to process or analyze groups of users.

Common scenarios include:

  • Synchronizing user lists from Agendor into another system.
  • Generating reports based on user data.
  • Filtering users by name or other criteria for targeted actions.

For example, you could use this node to fetch all users whose names contain "João Silva", ordered by creation date in descending order, retrieving 50 users per page.

Properties

Name Meaning
Options Collection of parameters to customize the query:
  Order By Field to sort results by. Options: ID, Nome (Name), Criado Em (Created At), Atualizado Em (Updated At)
  Order Direction Sort direction. Options: Crescente (Ascending), Decrescente (Descending)
  Page Page number to retrieve (minimum 1)
  Per Page Number of items per page (1 to 100, default 20)
  Search Search term to filter users by name or other searchable fields

Output

The node outputs JSON data containing an array of user objects retrieved from the Agendor API. Each user object typically includes fields such as user ID, name, email, and other user-related metadata as provided by the API.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Empty Results: If no users are returned, verify the search term and pagination settings. Also, ensure the API token has sufficient permissions.
  • Authentication Errors: Common errors include invalid or missing API tokens. Confirm the API key credential is correctly set up.
  • Rate Limits: The Agendor API may enforce rate limits; if exceeded, wait before retrying.
  • Invalid Parameter Values: Ensure numeric fields like page and perPage are within allowed ranges (page ≥ 1, perPage ≤ 100).

Links and References

Discussion