Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node interacts with the Chatwoot API to manage webhooks and other resources. Specifically, for the Webhook - Get operation, it retrieves details of a specific webhook by its numeric ID within a Chatwoot account.
Common scenarios where this node is beneficial include:
- Fetching configuration details of an existing webhook to verify or audit its settings.
- Integrating Chatwoot webhook data into workflows for monitoring or further processing.
- Automating management tasks that require reading webhook information before updates or deletions.
Practical example:
- You want to retrieve the URL and subscribed events of a webhook with ID 5 to confirm it is correctly set up before enabling or modifying it.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The numeric ID of the webhook to retrieve. |
| Continue on Fail | Whether the node should continue executing subsequent items if this operation fails. |
| Debug Logging | Whether to output detailed request and response logs to the console for debugging. |
Output
The node outputs the JSON response from the Chatwoot API representing the webhook's details. This typically includes fields such as the webhook's ID, URL, subscribed events, creation date, and other metadata.
If the operation succeeds, the output will be a JSON object with the webhook's properties.
If the operation fails and "Continue on Fail" is enabled, the output will contain an error message in the JSON under an error key.
The node does not output binary data.
Dependencies
- Requires an API authentication token credential for Chatwoot (an API key or access token).
- Needs the Chatwoot account ID and base URL configured in the credentials.
- Uses HTTP requests to communicate with the Chatwoot REST API.
Troubleshooting
Common issues:
- Invalid or missing webhook ID parameter.
- Incorrect or expired API authentication token.
- Network connectivity issues to the Chatwoot server.
- Insufficient permissions for the API token to read webhook data.
Error messages:
- HTTP errors returned by the Chatwoot API (e.g., 404 Not Found if webhook ID does not exist).
- JSON parsing errors if the API response is malformed (rare).
- Credential errors if the API token is invalid or missing.
Resolutions:
- Verify the webhook ID is correct and exists in the Chatwoot account.
- Ensure the API token credential is valid and has necessary permissions.
- Enable debug logging to see detailed request/response info for troubleshooting.
- Check network connectivity and Chatwoot server availability.