Agendor icon

Agendor

Trabalhe com dados da API do Agendor CRM

Overview

This node integrates with the Agendor CRM API to manage organizations. Specifically, the Delete operation under the Organization resource allows users to delete an existing organization by its ID. This is useful in scenarios where an organization record is no longer relevant or was created by mistake and needs to be removed from the CRM system.

Practical examples:

  • Automatically removing outdated or duplicate organization entries during data cleanup workflows.
  • Deleting organizations that have been marked as inactive or lost business opportunities.
  • Integrating with other systems to synchronize deletions of company records.

Properties

Name Meaning
Organization ID The numeric ID of the organization to delete. Example: 12345

Output

The node outputs the JSON response returned by the Agendor API after attempting to delete the organization. Typically, for a successful deletion, this might be an empty object or a confirmation message depending on the API's design.

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token credential for the Agendor CRM API.
  • The base URL used for requests is https://api.agendor.com.br/v3.
  • The node sends HTTP DELETE requests to the endpoint /organizations/{organizationId} where {organizationId} is replaced by the provided organization ID.

Troubleshooting

  • Common issues:

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

    • 401 Unauthorized: Check that the API token credential is correctly configured and valid.
    • 404 Not Found: The specified Organization ID does not exist; verify the ID.
    • 400 Bad Request: The Organization ID format may be incorrect; ensure it is numeric as expected.
  • Resolution tips:

    • Double-check the Organization ID input for correctness.
    • Verify API credentials and permissions.
    • Ensure the Agendor API service is reachable from your environment.

Links and References

Discussion