Actions113
- 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
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Contacts API Actions
- Inbox API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Custom Attributes Actions
- Canned Response Actions
Overview
This node operation deletes a specific integration hook from an account in the ChatWoot system. Integration hooks are typically used to connect ChatWoot with other services or automate workflows by triggering actions when certain events occur. Deleting an integration hook is useful when you want to remove outdated or unnecessary integrations, clean up your account, or stop automated processes linked to that hook.
Practical examples:
- Removing a webhook that sends notifications to an external service no longer in use.
- Cleaning up integration hooks after migrating to a new automation platform.
- Disabling integrations temporarily by deleting and later recreating hooks.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account from which the integration hook will be deleted. |
| Hook Id | The numeric ID of the specific integration hook to delete. |
Output
The output JSON contains the response from the API after attempting to delete the integration hook. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The node expects the base URL of the ChatWoot instance to be configured in the credentials.
- Network access to the ChatWoot API endpoint is necessary.
Troubleshooting
Common issues:
- Providing incorrect or non-existent Account Id or Hook Id will result in errors indicating the resource was not found.
- Missing or invalid API authentication token will cause authorization failures.
- Network connectivity problems can prevent the node from reaching the ChatWoot API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify that the API key credential is correctly set and has sufficient permissions.
- "Not Found": Check that both Account Id and Hook Id are correct and exist in the ChatWoot system.
- "Network Error": Ensure the n8n instance has internet access and the ChatWoot URL is reachable.