CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API

Overview

This node interacts with the CrunchzApp API to retrieve detailed information about a specific chat. It is designed to fetch chat details by using a unique contact identifier. This functionality is useful in scenarios where you need to access or display metadata and status related to a particular chat session, such as in customer support dashboards, CRM integrations, or automated messaging workflows.

For example, you might use this node to:

  • Retrieve the current state of a chat with a customer.
  • Access chat metadata for logging or analytics.
  • Verify if a chat exists before sending messages or performing other operations.

Properties

Name Meaning
Contact Id The unique identifier of the contact in the format xxx@c.us. This specifies which chat's details to retrieve.

Output

The node outputs JSON data containing the detailed information of the specified chat. This typically includes metadata fields such as chat status, timestamps, participants, and other relevant chat attributes provided by the CrunchzApp API.

If the API supports binary data (e.g., media attachments), the node would handle it accordingly, but based on the provided code and operation, the output focuses on JSON chat details.

Dependencies

  • Requires an active connection to the CrunchzApp API.
  • Needs an API key credential configured in n8n to authenticate requests.
  • The base URL for API requests is https://api.crunchz.app/api.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Invalid Contact Id: If the contact ID is malformed or does not exist, the API may return an error or empty response. Ensure the contact ID follows the expected format (xxx@c.us).
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up in n8n.
  • Network Issues: Connectivity problems can prevent the node from reaching the CrunchzApp API. Check network settings and API availability.
  • API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion