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 manage organization data. Specifically, the "Get Many" operation under the "Organization" resource retrieves multiple organizations from the CRM system. It supports filtering, pagination, and sorting of the results.

Common scenarios where this node is beneficial include:

  • Synchronizing a list of organizations from Agendor into another system.
  • Displaying or processing multiple organizations for reporting or analytics.
  • Automating workflows that require bulk access to organization data.

For example, you could use this node to fetch all organizations whose names match a search term, ordered by creation date, and process them in batches of 50 per page.

Properties

Name Meaning
Options Collection of optional parameters to customize the query:
- Order By Field to sort the results by. Options: ID, Name, Created At, Updated At
- Order Direction Direction of sorting. Options: Ascending (asc), Descending (desc)
- Page Page number to retrieve (minimum 1)
- Per Page Number of items per page (minimum 1, maximum 100)
- Search Search term to filter organizations by name or other searchable fields

Output

The node outputs JSON data containing an array of organization objects retrieved from the Agendor API. Each object represents an organization with its properties as defined by the API (such as id, name, created_at, updated_at, etc.).

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential to connect to the Agendor API.
  • The base URL used is https://api.agendor.com.br/v3.
  • The node sends requests with appropriate headers including Accept: application/json and Content-Type: application/json.
  • Query parameters are dynamically set based on the input options for filtering, pagination, and sorting.

Troubleshooting

  • Empty Results: If no organizations are returned, verify the search term and pagination parameters. Also check if your API token has sufficient permissions.
  • Invalid Parameter Errors: Ensure that numeric inputs like page and perPage are within allowed ranges (page ≥ 1, perPage ≤ 100).
  • Authentication Failures: Confirm that the API token credential is correctly configured and valid.
  • Rate Limits: The API may limit the number of requests; consider adding delays or handling rate limit errors gracefully.

Links and References

Discussion