Actions7
- Action Actions
- Chatbot Actions
Overview
The node interacts with a chat data service API to retrieve conversations related to a specified chatbot. Specifically, the "Get Conversations" operation fetches conversation records for a given chatbot, optionally filtered by lead ID, date range, and source channel. This is useful for scenarios where you want to analyze or process chat interactions, such as customer support transcripts, chatbot performance reviews, or lead engagement tracking.
Practical examples include:
- Extracting recent conversations from a chatbot to feed into analytics dashboards.
- Filtering conversations by source (e.g., Slack, WhatsApp) to understand channel-specific user behavior.
- Retrieving conversations within a specific timeframe for compliance or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Chatbot Name or ID | Select the chatbot from a list or specify its ID to identify which chatbot's conversations to fetch. |
| Limit | Maximum number of conversation results to return. |
| Additional Fields | Optional filters to refine the query: |
| - Lead ID | Filter conversations associated with a specific lead identified by this unique ID. |
| - Start Date | Retrieve conversations created after this date/time. |
| - End Date | Retrieve conversations created before this date/time. |
| - Source | Filter conversations by their origin/source channel. Options include: All Sources, API, Chat Data Site, Discord, Iframe, Messenger, Slack, WhatsApp, Widget. |
Output
The output consists of individual conversation objects returned in the json field for each item. Each object represents a conversation record retrieved from the chat data service. The structure includes all relevant conversation details as provided by the API, such as conversation metadata, messages, timestamps, and associated lead information if available.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the chat data service.
- The node expects a base URL for the chat data API to be set in the credentials.
- Network access to the chat data API endpoint is necessary.
Troubleshooting
- Missing Base URL in Credentials: If the base URL is not set in the API credentials, the node will throw an error indicating this. Ensure the credentials are properly configured with the correct base URL.
- API Errors: If the API returns an error status, the node surfaces the error message. Common causes include invalid chatbot ID, exceeding rate limits, or malformed requests. Verify input parameters and API key validity.
- Invalid Response Format: If the response does not contain the expected conversations array, the node will raise an error. This might indicate an API change or connectivity issue.
- Limit Exceeded: Setting a very high limit may cause performance issues or timeouts. Use reasonable limits and paginate if needed.
- Date Filters: Ensure that start and end dates are valid ISO date strings; otherwise, filtering may not work as expected.
If the node is set to continue on fail, errors for individual items will be included in the output JSON under an error property instead of stopping execution.
Links and References
- n8n Expressions Documentation
- Chat data service API documentation (not publicly linked here; refer to your service provider's docs)