Actions113
- 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
- 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
Overview
This node interacts with the ChatWoot API to retrieve detailed information about a single Agent Bot. It is useful when you need to fetch specific data about an individual agent bot configured in your ChatWoot workspace, such as its settings, status, or metadata.
Practical examples include:
- Displaying detailed info about a particular agent bot in a dashboard.
- Using the agent bot details to make decisions in automated workflows.
- Auditing or logging agent bot configurations for compliance or troubleshooting.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the agent bot whose details you want to retrieve. This property is required. |
Output
The node outputs JSON data containing the full details of the specified agent bot as returned by the ChatWoot API. This typically includes fields such as the agent bot's ID, name, status, configuration, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL of 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:
- Providing an invalid or non-existent agent bot ID will result in an error from the API indicating that the resource was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent the node from reaching the ChatWoot API.
Error messages:
- "Agent bot not found": Verify that the provided ID corresponds to an existing agent bot.
- "Authentication failed": Check that the API key credential is correctly set up and has sufficient permissions.
- Timeout or network errors: Ensure that the ChatWoot server URL is reachable from the n8n environment.