Chat Data icon

Chat Data

Basic Chat Data Node

Actions8

Action → Get Conversations

AI-generated

Overview

This node operation retrieves conversations from a specified chatbot. It allows filtering conversations by lead ID, date range (start and end dates), and source platform (e.g., API, Messenger, Slack). The node supports pagination internally to fetch up to the specified limit of conversations.

Use Case Examples

  1. A user wants to analyze recent conversations from a chatbot on Messenger to improve customer support.
  2. A user needs to export conversations filtered by a specific lead ID for auditing purposes.

Properties

Name Meaning
Chatbot Name or ID The identifier of the chatbot from which to retrieve conversations. This can be selected from a list or specified via an expression.
Limit The maximum number of conversation results to return. Must be at least 1.
Lead ID Optional filter to retrieve conversations associated with a specific lead ID.
Start Date Optional filter to retrieve conversations created after this date.
End Date Optional filter to retrieve conversations created before this date.
Source Optional filter to retrieve conversations from a specific source platform such as API, Messenger, Slack, etc.

Output

JSON

  • json
    • conversationId - Unique identifier of the conversation.
    • leadId - Identifier of the lead associated with the conversation.
    • source - Source platform of the conversation.
    • createdAt - Timestamp when the conversation was created.
    • messages - Array of messages within the conversation.

Dependencies

  • An API key credential for authentication to the Chat Data API, including a base URL.

Troubleshooting

  • Ensure the chatbot ID is valid and exists; otherwise, the API will return an error.
  • Check that the API key credential is correctly configured with a valid base URL and API key.
  • If the node returns an error status, inspect the error message for details such as invalid parameters or API limits.
  • The node handles pagination internally, but if the limit is very high, the API or network might timeout or fail; consider lowering the limit.

Discussion