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 activity records. The "Get Many" operation under the "Activity" resource allows users to list activities or tasks stored in their Agendor account, supporting filtering, pagination, and sorting.

Common scenarios where this node is beneficial include:

  • Fetching a list of scheduled calls, meetings, or tasks for sales or support teams.
  • Retrieving activities filtered by search terms to monitor customer interactions.
  • Paginating through large sets of activities to process or analyze them in batches.
  • Sorting activities by creation date, update date, or name to prioritize follow-ups.

Practical example: A user wants to get all activities related to a specific client or within a certain timeframe, sorted by the most recent update, to prepare for a sales meeting.

Properties

Name Meaning
Options Collection of optional parameters to customize the retrieval of activities:
- Order By Field to sort results by: ID, Name, Created At, or Updated At
- Order Direction Direction of sorting: Ascending or 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 activities by text

Output

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

  • id: Unique identifier of the activity
  • type: Type of activity (call, email, meeting, note, task)
  • text: Description or content of the activity
  • datetime: Date and time associated with the activity
  • Related entity IDs (deal, person, organization, user)

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Empty results: Ensure that the search term and filters are correct and that there are activities matching the criteria.
  • Invalid page or perPage values: Use valid numbers within allowed ranges (page ≥ 1, perPage between 1 and 100).
  • Authentication errors: Verify that the API token credential is correctly set up and has sufficient permissions.
  • API rate limits: If many requests are made rapidly, the API might throttle; implement delays or reduce request frequency.
  • Unexpected response structure: Confirm that the Agendor API version matches the expected schema.

Links and References

Discussion