CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API
Join our community

Actions22

Overview

This node integrates with the CrunchzApp API to retrieve chat data. Specifically, for the "Chat" resource and the "All Chat" operation, it fetches a list of chat entries with pagination support through limit and offset parameters. This is useful in scenarios where you want to display or process multiple chat records from CrunchzApp, such as building dashboards, exporting chat logs, or analyzing conversation history.

Example use cases:

  • Fetching recent chats for customer support analysis.
  • Exporting chat conversations for backup or reporting.
  • Displaying paginated chat lists in an automation workflow.

Properties

Name Meaning
Limit Number of chat records to fetch (pagination limit).
Offset Starting position in the chat list (pagination offset).

Output

The node outputs JSON data containing the list of chat records retrieved from the CrunchzApp API. Each item in the output corresponds to a chat entry with its associated details as provided by the API. The exact structure depends on the API response but typically includes chat identifiers, timestamps, participants, and message summaries.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the CrunchzApp API.
  • The node uses the base URL https://api.crunchz.app/api for requests.
  • No additional external dependencies beyond the CrunchzApp API and n8n's HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Providing negative or non-integer values for Limit or Offset may result in API errors or unexpected results.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication failures usually indicate invalid API keys; verify and update credentials.
    • Rate limiting or quota exceeded errors suggest too many requests; consider adding delays or reducing frequency.
    • Unexpected API responses might require checking if the CrunchzApp API has changed or if the node version is outdated.

Links and References

Discussion