ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node allows users to delete a specific custom filter from an account in the ChatWoot system. Custom filters are typically used to organize or segment data such as conversations or contacts based on user-defined criteria. Deleting a custom filter is useful when it is no longer needed or relevant, helping keep the filtering options clean and up-to-date.

Practical examples:

  • Removing outdated or obsolete filters that no longer apply to current workflows.
  • Cleaning up filters after restructuring account segmentation.
  • Automating maintenance tasks to delete filters created temporarily during batch operations.

Properties

Name Meaning
Account Id The numeric ID of the account from which the custom filter will be deleted.
Custom Filter Id The numeric ID of the custom filter to delete.

Output

The output JSON contains the response from the API after attempting to delete the specified custom filter. Typically, this would include confirmation of deletion or details about the operation's success or failure.

If the node supports binary data output, it is not indicated here; thus, the output is expected to be purely JSON-based.

Dependencies

  • Requires an API key credential for authenticating with the ChatWoot API.
  • Needs the base URL of the ChatWoot instance configured in the credentials.
  • Depends on the ChatWoot REST API being accessible and operational.

Troubleshooting

  • Common issues:

    • Invalid or missing Account Id or Custom Filter Id can cause the deletion to fail.
    • Insufficient permissions associated with the API key may prevent deletion.
    • Network connectivity problems or incorrect base URL configuration can lead to request failures.
  • Error messages:

    • "Not Found" or similar errors indicate the specified custom filter or account does not exist.
    • "Unauthorized" errors suggest invalid or expired API credentials.
    • "Bad Request" errors may occur if input parameters are malformed or missing.
  • Resolutions:

    • Verify that the Account Id and Custom Filter Id are correct and correspond to existing entities.
    • Ensure the API key has sufficient permissions to delete custom filters.
    • Check network settings and confirm the base URL is correctly set in the credentials.

Links and References

Discussion