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 activities (tasks, calls, emails, meetings, notes) within a sales or customer relationship context. Specifically, the Activity - Get operation retrieves detailed information about a single activity by its unique ID.

Typical use cases include:

  • Fetching details of a specific task or meeting scheduled in the CRM.
  • Retrieving an activity’s description, type, date/time, and related entities (deal, person, organization, user).
  • Automating workflows that require up-to-date activity data from Agendor for reporting or follow-up actions.

For example, you might use this node to get the details of a call logged in the CRM before triggering a notification or updating another system.

Properties

Name Meaning
Activity ID The unique identifier of the activity to retrieve. This is required to specify which activity's details to fetch.

Output

The node outputs JSON data representing the requested activity object as returned by the Agendor API. This typically includes fields such as:

  • id: Activity identifier
  • type: Type of activity (call, email, meeting, note, task)
  • text: Description or notes about the activity
  • datetime: Scheduled date and time of the activity
  • Related entity IDs: deal_id, person_id, organization_id, user_id
  • Other metadata provided by the API

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authorize requests to the Agendor API.
  • The base URL used is https://api.agendor.com.br/v3.
  • The node sends HTTP GET requests to /activities/{activityId} endpoint.

Troubleshooting

  • Missing or invalid Activity ID: The operation requires a valid activity ID. If omitted or incorrect, the API will return an error indicating the resource was not found.
  • Authentication errors: Ensure the API token credential is correctly set up and has sufficient permissions.
  • Network issues: Connectivity problems may cause request failures; verify network access to the Agendor API.
  • API rate limits: Excessive requests may be throttled by the API; handle such errors by retrying after some delay.

Common error messages:

  • 404 Not Found: The specified activity ID does not exist.
  • 401 Unauthorized: Invalid or missing API token.
  • 400 Bad Request: Malformed request parameters.

Resolving these usually involves verifying input parameters, credentials, and network connectivity.

Links and References

Discussion