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 "Person" resources, specifically allowing deletion of a person record by their ID. It is useful in scenarios where you need to automate the removal of contact or person data from your CRM system, for example, when cleaning up outdated contacts or complying with data privacy requests.

Practical example: Automatically delete a person from Agendor CRM after they unsubscribe from your mailing list or when their data is no longer relevant.

Properties

Name Meaning
Person ID The numeric ID of the person to delete. This identifies which person record will be removed.

Output

The node outputs JSON data representing the response from the Agendor API after attempting to delete the specified person. Typically, a successful delete operation returns an empty body or confirmation status. No binary data output is expected.

Dependencies

  • Requires an API authentication token credential for Agendor CRM.
  • The node sends HTTP DELETE requests to the Agendor API endpoint https://api.agendor.com.br/v3/people/{personId}.
  • Proper configuration of the API key credential in n8n is necessary for authorization.

Troubleshooting

  • Common issues:

    • Invalid or missing Person ID: The node requires a valid numeric ID; ensure this is provided.
    • Authentication errors: Verify that the API token credential is correctly set and has sufficient permissions.
    • Network or API downtime: Check connectivity and Agendor service status if requests fail.

  • Error messages:

    • Unauthorized (401): Indicates invalid or missing API token. Resolve by updating credentials.
    • Not Found (404): The specified Person ID does not exist. Confirm the ID is correct.
    • Bad Request (400): Usually due to malformed request parameters. Ensure the Person ID is properly formatted.

Links and References

Discussion