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 tags, specifically allowing users to retrieve multiple tags with filtering and pagination options. The "Get Many" operation under the "Tag" resource fetches a list of tags from the CRM system, supporting sorting, paging, and search filtering.

Common scenarios where this node is beneficial include:

  • Synchronizing tag data from Agendor CRM into other systems or databases.
  • Displaying a filtered and paginated list of tags in dashboards or reports.
  • Automating workflows that depend on tag metadata, such as categorization or tagging rules.

Practical example:

  • A sales automation workflow retrieves all tags sorted by creation date in descending order, filtered by a search term like "priority", to assign relevant tags to new deals automatically.

Properties

Name Meaning
Options Collection of optional parameters to customize the retrieval of tags:
- 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 tags by name or other searchable fields

Output

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

  • id: Unique identifier of the tag
  • name: Name of the tag
  • color: Hexadecimal color code associated with the tag
  • created_at: Timestamp when the tag was created
  • updated_at: Timestamp when the tag was last updated

No binary data output is involved in this operation.

Dependencies

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

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 or pagination parameters might result in API errors.

  • Error messages and resolutions:

    • 401 Unauthorized: Check if the API token credential is correctly set and valid.
    • 400 Bad Request: Verify that query parameters like order_by, order_direction, page, and per_page are within allowed values.
    • 429 Too Many Requests: The API rate limit has been exceeded; implement retry logic or reduce request frequency.

Links and References

Discussion