ChatWoot icon

ChatWoot

Interact with ChatWoot API

Actions113

Overview

This node operation updates an existing webhook in the ChatWoot system. It allows users to modify the URL where webhook events are sent and adjust the list of event subscriptions for that webhook. This is useful when you want to change the destination endpoint for webhook notifications or update which events trigger those notifications without creating a new webhook from scratch.

Practical examples:

  • Changing the webhook URL after migrating your event handling service to a new domain.
  • Updating the subscribed events to add or remove certain event types based on evolving integration needs.

Properties

Name Meaning
Account Id The numeric ID of the account owning the webhook.
Webhook Id The numeric ID of the webhook to update.
Url The new URL where the webhook events should be sent.
Subscriptions A JSON array specifying the events to subscribe to for this webhook (e.g., message.created, conversation.status_changed).

Output

The node outputs JSON data representing the updated webhook object as returned by the ChatWoot API. This typically includes details such as the webhook's ID, URL, subscribed events, status, and timestamps. There is no binary output.

Dependencies

  • Requires an API key credential for authenticating with the ChatWoot API.
  • The base URL for the ChatWoot instance must be configured in the credentials.
  • The node uses HTTP requests to interact with the ChatWoot REST API.

Troubleshooting

  • Invalid Account or Webhook ID: If the provided IDs do not exist or belong to another user, the API will return an error. Verify the IDs are correct.
  • Malformed Subscriptions JSON: The subscriptions property expects valid JSON. Invalid JSON will cause parsing errors. Ensure the JSON syntax is correct.
  • Unauthorized Access: Missing or invalid API credentials will result in authentication errors. Confirm the API key and base URL are correctly set.
  • URL Validation: The webhook URL should be a valid and reachable endpoint. Invalid URLs may cause the API to reject the update.

Links and References

Discussion