Actions16
- Conversation Actions
- Todo Actions
- Fact Actions
- Location Actions
Overview
The node interacts with the BeeAI API to list conversations. It fetches a paginated list of conversation records from the BeeAI service, allowing users to retrieve multiple conversation entries in a controlled manner. This is useful for scenarios where you want to analyze, display, or process batches of conversations, such as customer support chat logs, AI-generated dialogues, or any conversational data managed by BeeAI.
Practical examples include:
- Retrieving recent conversations for review or reporting.
- Fetching conversations page-by-page to display in a user interface.
- Integrating conversation data into workflows for further processing or analysis.
Properties
| Name | Meaning |
|---|---|
| Pagination | Collection of pagination options: |
| - Page Number | The page number to fetch (minimum 1). |
| - Number of Items per Page | Maximum number of results to return per page (minimum 1). |
Output
The node outputs JSON data representing a list of conversations retrieved from the BeeAI API. Each item in the output corresponds to a single conversation record with its associated details as provided by the API.
If the API supports binary data related to conversations (e.g., attachments), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON-formatted conversation data.
Dependencies
- Requires an API key credential for authenticating with the BeeAI API.
- The base URL for API requests is
https://api.bee.computer. - The node expects the BeeAI API to support query parameters for pagination (
pageandlimit).
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Requesting a page number beyond available pages may return empty results.
- Setting
limittoo high might lead to performance issues or API rate limiting.
Error messages:
- Authentication errors typically indicate invalid credentials; verify the API key.
- HTTP errors related to bad requests may result from invalid pagination values; ensure
pageandlimitare positive integers. - Network errors suggest connectivity issues; check internet connection and API availability.
Links and References
- BeeAI API Documentation (assumed base URL, please refer to official docs)
- n8n documentation on pagination handling