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
Account Agent Bots → Update An Account Agent Bot
AI-generatedOverview
This node operation updates an existing Account Agent Bot within a specified account. It allows users to modify details such as the bot's name, description, and webhook URL. This is useful in scenarios where you need to maintain or improve your automated agents by changing their metadata or integration endpoints without recreating them.
Practical examples include:
- Changing the outgoing webhook URL when the bot’s backend service endpoint changes.
- Updating the bot’s name or description to reflect new functionalities or branding.
- Correcting typos or adding more descriptive information about the bot.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account to which the agent bot belongs. |
| Id | The unique identifier of the agent bot that needs to be updated. |
| Name | The new name for the agent bot. |
| Description | A textual description providing details about the agent bot. |
| Outgoing Url | The webhook URL where the bot sends outgoing requests or notifications. |
Output
The node outputs JSON data representing the updated state of the Account Agent Bot after the update operation completes successfully. This typically includes the bot’s identifiers, updated fields (name, description, outgoing URL), and possibly status or metadata returned from the API.
If the node supports binary data output, it would relate to any files or media associated with the bot, but based on the provided code and properties, this operation focuses solely on JSON data updates.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- Needs the base URL of the ChatWoot instance configured in the credentials.
- Depends on the ChatWoot API being accessible and the user having permissions to update agent bots within the specified account.
Troubleshooting
- Invalid Account Id or Bot Id: If the provided IDs do not exist or are incorrect, the API will likely return a "not found" error. Verify the IDs before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node credentials.
- Validation Errors: Providing invalid URLs or empty required fields may result in validation errors from the API. Double-check the format and presence of required inputs.
- Network Issues: Connectivity problems to the ChatWoot server can cause timeouts or connection errors. Confirm network access and server availability.
Links and References
- ChatWoot API Documentation — For detailed API endpoints and payload structures.
- n8n Documentation — For general guidance on using and configuring nodes and credentials.