ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node allows users to delete a specific webhook from their ChatWoot account by providing the account ID and the webhook ID. It is useful for managing webhooks, especially when you want to remove outdated or unnecessary webhook configurations to keep your integrations clean and secure.

Practical examples include:

  • Removing a webhook that is no longer needed after a project ends.
  • Deleting a webhook that was created incorrectly or is causing errors.
  • Managing webhook lifecycle programmatically as part of automation workflows.

Properties

Name Meaning
Account Id The numeric ID of the ChatWoot account where the webhook exists. This identifies which account's webhook will be deleted.
Webhook Id The numeric ID of the webhook to delete. This specifies exactly which webhook to remove from the account.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this would confirm whether the webhook was successfully deleted or provide error information if the deletion failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating with the ChatWoot API.
  • The node uses the ChatWoot API base URL configured in the credentials.
  • Network access to the ChatWoot API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Providing incorrect or non-existent Account Id or Webhook Id will cause the deletion to fail.
    • Missing or invalid API authentication token will prevent the request from succeeding.
    • Network connectivity problems can cause timeouts or failures.
  • Error messages:

    • "Webhook not found" indicates the specified webhook ID does not exist under the given account.
    • "Unauthorized" or "Authentication failed" means the API key is missing, invalid, or expired.
    • "Bad Request" may indicate malformed input parameters.
  • Resolutions:

    • Verify the Account Id and Webhook Id are correct and correspond to existing resources.
    • Ensure the API key credential is properly set up and has sufficient permissions.
    • Check network connectivity and retry the operation.

Links and References

Discussion