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 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 configuration, 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 identifier (ID) of the agent bot whose details you want to retrieve. This is a required numeric value. |
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 bot's ID, name, status, configuration settings, and other metadata relevant to the agent bot.
No binary data output is produced by this operation.
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
- Invalid or missing Id: Ensure the "Id" property is provided and corresponds to an existing agent bot in ChatWoot.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Confirm that the ChatWoot instance URL is reachable from the n8n environment.
- API changes: If the ChatWoot API changes, the node might fail; check for updates or compatibility notes.