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 delete a tag by its ID. It is useful in scenarios where you need to programmatically remove tags that are no longer relevant or were created by mistake within your CRM system.

For example, if you have automated workflows that categorize contacts or deals with tags and later want to clean up unused or obsolete tags, this node operation can be used to delete those tags efficiently.

Properties

Name Meaning
Tag ID The unique identifier of the tag to delete (string). This is required to specify which tag should be removed.

Output

The output JSON typically contains the response from the Agendor API after attempting to delete the tag. Since this is a DELETE operation, the response may be empty or contain a confirmation message indicating successful deletion.

No binary data output is expected for this operation.

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/tags/{tagId}.
  • Proper configuration of the API token in n8n credentials is necessary for authorization.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent Tag ID will result in an error from the API.
    • Missing or incorrect API authentication token will cause authorization failures.
    • Network connectivity issues can prevent the request from reaching the API.

  • Error Messages:

    • 404 Not Found: The specified Tag ID does not exist. Verify the Tag ID is correct.
    • 401 Unauthorized: Authentication failed due to missing or invalid API token. Check your API credentials.
    • 400 Bad Request: The request was malformed; ensure the Tag ID is provided and correctly formatted.

  • Resolution Tips:

    • Double-check the Tag ID input for correctness.
    • Ensure the API token credential is set up properly in n8n.
    • Test connectivity to the Agendor API endpoint outside n8n to rule out network issues.

Links and References

Discussion