Actions23
- Channel Actions
- Message Actions
- Contact Actions
- Tickets Actions
Overview
This node interacts with the Bizwachat API to retrieve information about a specific conversation within a channel by its unique identifier (UUID). It is useful when you need to fetch detailed data about a particular conversation, such as messages or metadata, for further processing or analysis in your workflow.
Practical examples include:
- Fetching conversation details to display in a dashboard.
- Retrieving conversation history for customer support automation.
- Integrating conversation data into CRM or analytics tools.
Properties
| Name | Meaning |
|---|---|
| Uuid | The unique identifier of the conversation to retrieve. This is a required string input that specifies which conversation's details will be fetched from the Bizwachat API. |
Output
The node outputs JSON data representing the conversation details retrieved from the Bizwachat API. This typically includes all relevant information about the conversation identified by the provided UUID, such as messages, participants, timestamps, and any associated metadata.
If the API supports binary data (e.g., attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is structured JSON data.
Dependencies
- Requires an active connection to the Bizwachat API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- The base URL for API requests is
https://bizwachat.com. - The node expects JSON responses and sends requests with appropriate headers (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Invalid or missing UUID: Ensure the UUID property is correctly set and corresponds to an existing conversation; otherwise, the API may return an error or empty result.
- Authentication errors: Verify that the API key or authentication token is valid and properly configured in the node credentials.
- Network issues: Check connectivity to
https://bizwachat.comand ensure no firewall or proxy blocks the request. - API rate limits: If many requests are made in a short time, the API might throttle or reject calls; consider implementing retries or delays.
- Unexpected response format: Confirm that the API version matches the node implementation to avoid schema mismatches.
Links and References
- Bizwachat Official Website
- Bizwachat API Documentation (assumed location for API docs)