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 data related to people (contacts). Specifically, the "Person - Get" operation retrieves detailed information about a single person/contact by their numeric ID. This is useful in scenarios where you want to fetch up-to-date contact details from your CRM system for use in workflows such as sending personalized emails, updating records, or syncing contact data with other systems.

Practical example:
You have a workflow that triggers when a deal is updated, and you want to fetch the associated person's full details to send them a notification email. Using this node's "Get Person" operation, you provide the person's ID, retrieve their data, and then use it downstream in your automation.

Properties

Name Meaning
Person ID The unique numeric identifier of the person/contact to retrieve. Example: 12345

Output

The node outputs JSON data representing the person/contact retrieved from the Agendor CRM. The structure typically includes fields such as:

  • id: Numeric ID of the person
  • name: Full name of the person
  • email: Email address
  • Other possible contact details like phone number, CPF (tax ID), address, etc., depending on what is stored in the CRM.

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the Agendor CRM API.
  • The node makes HTTP GET requests to the endpoint /people/{personId} on the base URL https://api.agendor.com.br/v3.

Troubleshooting

  • Common issues:

    • Invalid or missing Person ID: The node requires a valid numeric ID; providing an empty or incorrect ID will cause errors.
    • Authentication failures: If the API token is invalid or missing, the request will be rejected.
    • Network or API downtime: Temporary connectivity issues can cause request failures.

  • Common error messages:

    • 404 Not Found: The specified person ID does not exist in the CRM. Verify the ID is correct.
    • 401 Unauthorized: Authentication failed due to invalid or missing API token. Check credentials configuration.
    • 400 Bad Request: The input parameters are malformed or missing required fields.

To resolve these, ensure the Person ID is correct, the API token credential is properly set up, and the Agendor API service is operational.

Links and References

Discussion