Actions36
- Account Actions
- Canned Response Actions
- Contact Actions
- Conversation Actions
- Inbox Actions
- Label Actions
- Message Actions
- Team Actions
- Webhook Actions
Overview
This node interacts with the Chatwoot API to manage conversations and related entities. Specifically, for the Conversation - Get operation, it retrieves detailed information about a single conversation by its numeric ID within a Chatwoot account.
Use cases include:
- Fetching the current state and details of a specific customer support conversation.
- Integrating conversation data into workflows for reporting, analytics, or triggering other actions based on conversation content or status.
- Automating follow-ups or updates by retrieving conversation metadata.
Example: You want to get all details of conversation #12345 to check its status, assigned agent, messages, and custom attributes before deciding the next workflow step.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The numeric ID of the conversation you want to retrieve. This is required. |
| Continue on Fail | Whether the node should continue processing subsequent items if this operation fails. |
| Debug Logging | Enables console logging of request details for debugging purposes. |
Output
The output is a JSON object representing the full details of the requested conversation as returned by the Chatwoot API. This includes fields such as conversation status, assignee, contact info, messages, labels, custom attributes, timestamps, and other metadata.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Chatwoot API.
- Needs the Chatwoot account ID and base URL configured in the credentials.
- The node makes HTTP GET requests to the Chatwoot REST API endpoint
/api/v1/accounts/{accountId}/conversations/{conversationId}.
Troubleshooting
- Invalid Conversation ID: If the provided conversation ID does not exist or is incorrect, the API will return an error. Verify the ID is correct.
- Authentication Errors: Ensure the API key credential is valid and has access to the specified account.
- Network Issues: Check connectivity to the Chatwoot instance URL.
- JSON Parsing Errors: Not applicable here since this operation only performs a GET request without user-provided JSON input.
- Enable "Debug Logging" to see detailed request and response logs in the console, which helps diagnose issues.
If "Continue on Fail" is disabled (default), the node will stop execution on errors; enabling it allows processing of multiple items even if some fail.