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
- Webhooks Actions
- Teams Actions
- Custom Filters Actions
- Reports Actions
Overview
This node interacts with the ChatWoot API to delete a custom attribute from a specified account. It is useful in scenarios where you need to programmatically manage and clean up custom attributes associated with user accounts, such as removing outdated or incorrect metadata.
For example, if your system tracks additional user information via custom attributes and some attributes become obsolete or were added by mistake, this node allows you to remove those attributes efficiently without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account from which the custom attribute will be deleted. |
| Id | The ID of the custom attribute that you want to delete from the specified account. |
Output
The node outputs JSON data representing the response from the ChatWoot API after attempting to delete the custom attribute. Typically, this will include confirmation of deletion or error details if the operation failed.
No binary data output is expected from this node.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node depends on the
@devlikeapro/n8n-openapi-nodepackage for OpenAPI integration.
Troubleshooting
Common issues:
- Invalid or missing account ID or custom attribute ID will cause the API call to fail.
- Incorrect or expired API authentication token will result in authorization errors.
- Network connectivity problems can prevent the node from reaching the ChatWoot API.
Error messages:
- "Unauthorized" or "Authentication failed": Check that the API key credential is correctly set and valid.
- "Not Found": Verify that both the account ID and custom attribute ID exist in ChatWoot.
- "Bad Request": Ensure that the IDs are numeric and properly formatted.
Resolving these typically involves verifying input parameters, refreshing credentials, and ensuring network access.