Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Teams Actions
- Custom Filters Actions
- Webhooks Actions
- Reports Actions
Overview
This node operation allows you to create an integration hook within a specified account in the ChatWoot platform. Integration hooks enable external applications or services to receive event notifications or interact with ChatWoot data programmatically. This is useful for automating workflows, syncing data between ChatWoot and other tools, or triggering custom actions when certain events occur in ChatWoot.
Practical examples include:
- Creating a webhook that notifies your CRM system whenever a new conversation starts.
- Setting up an inbox-specific hook to forward messages to a third-party analytics service.
- Configuring app-level integration hooks to automate ticket creation or updates based on ChatWoot events.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the ChatWoot account where the integration hook will be created. |
| App Id | The identifier of the app for which the integration hook is being created (optional). |
| Inbox Id | The identifier of the inbox if the integration hook is specific to an inbox (optional). |
| Settings | JSON object containing configuration settings required by the integration hook. |
Output
The node outputs JSON data representing the newly created integration hook as returned by the ChatWoot API. This typically includes details such as the hook's unique ID, associated account, app or inbox IDs, and its configured settings.
If the integration hook involves binary data (not indicated here), it would be included in the binary output field; however, this operation primarily deals with JSON data.
Dependencies
- Requires an active connection to the ChatWoot API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the ChatWoot instance must be set in the credentials.
Troubleshooting
- Missing or invalid Account Id: Ensure the Account Id is provided and corresponds to an existing ChatWoot account.
- Invalid JSON in Settings: The "Settings" property expects valid JSON. Malformed JSON will cause errors; validate the JSON format before execution.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API endpoint issues: Confirm the base URL is correct and the ChatWoot server is reachable.
Common error messages may include HTTP 401 Unauthorized (authentication failure), HTTP 400 Bad Request (invalid parameters), or HTTP 404 Not Found (account or resource does not exist).