Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Chatwoot API, enabling users to manage various Chatwoot resources such as accounts, contacts, conversations, messages, inboxes, canned responses, webhooks, teams, and labels. Specifically, for the Webhook resource with the Get Many operation, the node fetches a list of all webhooks associated with a Chatwoot account.
Use cases include:
- Retrieving all configured webhooks to monitor or audit webhook endpoints.
- Automating workflows that depend on webhook configurations.
- Synchronizing webhook data between Chatwoot and other systems.
Example: You want to get all webhooks set up in your Chatwoot account to verify which URLs are receiving event notifications or to update your monitoring system accordingly.
Properties
| Name | Meaning |
|---|---|
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Whether to output detailed request and response information to the console for debugging. |
These properties control error handling behavior and logging verbosity during execution.
Output
The node outputs an array of JSON objects representing webhooks. Each object corresponds to a webhook retrieved from the Chatwoot API and contains details such as webhook ID, URL, subscribed events, and other metadata as returned by the API.
If multiple webhooks exist, the output is an array where each element has a json property holding one webhook's data.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Chatwoot API.
- The node expects the Chatwoot account ID and base URL to be provided via credentials.
- Network access to the Chatwoot API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Incorrect account ID or base URL in credentials can lead to failed requests.
- Network connectivity problems may prevent successful API calls.
Error messages:
- HTTP request failures will throw errors with messages indicating the problem (e.g., "Unauthorized", "Not Found").
- If debug logging is enabled, detailed error stack traces and request info will be printed to the console to aid diagnosis.
Resolution tips:
- Verify that the API key credential is correctly configured and active.
- Confirm the account ID and base URL match your Chatwoot instance.
- Enable debug logging to get more insight into request/response details.
- Check network/firewall settings to ensure connectivity to the Chatwoot API.
Links and References
- Chatwoot API Documentation – Official API reference for understanding webhook endpoints and payloads.
- n8n Documentation – General guidance on using n8n nodes and managing credentials.