Reachkit icon

Reachkit

Interact with the Reachkit API

Actions20

Conversation → Get Many

AI-generated

Overview

The node interacts with the Reachkit API to retrieve multiple conversation records. It is designed to fetch a list of conversations, optionally filtered and paginated, from the Reachkit platform. This operation is useful when you want to analyze, display, or process multiple conversations at once, such as for reporting, monitoring customer interactions, or integrating conversation data into other workflows.

Practical examples include:

  • Retrieving all conversations in the "Primary" folder to monitor active customer chats.
  • Searching conversations by keywords to find specific topics or issues.
  • Limiting the number of conversations fetched to optimize performance in dashboards.

Properties

Name Meaning
Return All Whether to return all available conversations or limit the results to a specified number.
Limit Maximum number of conversations to return if not returning all (1 to 100).
Additional Fields Optional filters and pagination controls:
- Page The page number of results to retrieve (for pagination).
- Search A search term to filter conversations by matching text.
- Folder Filter conversations by folder; options are "Primary" or "Others".

Output

The output contains a JSON array of conversation objects retrieved from the Reachkit API. Each object represents a conversation with its associated metadata and content as provided by the API.

If binary data were supported, it would typically represent attachments or media within conversations, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Reachkit API.
  • The node sends requests to https://reachkit.ai/api/v1.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Common Issues:

    • Authentication errors due to missing or invalid API credentials.
    • Exceeding rate limits imposed by the Reachkit API.
    • Invalid parameter values, such as setting Limit outside the allowed range (1-100).
    • Pagination errors if requesting pages beyond available data.

  • Error Messages:

    • Unauthorized or 401 errors indicate problems with the API key; verify and update credentials.
    • 400 Bad Request errors may result from invalid query parameters; check property values.
    • Empty results might mean no conversations match the search or folder filter; try adjusting filters.

Links and References

Discussion