CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API
Join our community

Actions22

Overview

The node provides an integration with the CrunchzApp API, specifically allowing users to interact with chat-related functionalities. The "Archive Chat" operation enables archiving a specific chat by providing the contact ID of the chat to be archived. This is useful in scenarios where users want to organize or clean up their chat list by moving inactive or completed conversations into an archive state.

Practical examples include:

  • Automatically archiving chats after a support ticket is resolved.
  • Archiving old customer conversations to keep the active chat list manageable.
  • Integrating with workflows that manage chat lifecycle based on external triggers.

Properties

Name Meaning
Contact Id The unique identifier of the contact whose chat should be archived. Format example: xxx@c.us.

Output

The node outputs JSON data representing the response from the CrunchzApp API after attempting to archive the specified chat. This typically includes confirmation of the archive action or any relevant status information returned by the API.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the CrunchzApp API.
  • The base URL for API requests is https://api.crunchz.app/api.
  • The node expects the API to accept and return JSON-formatted data.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact Id: Ensure the Contact Id is provided and correctly formatted (e.g., xxx@c.us).
    • Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
    • Network or API availability issues: Confirm that the CrunchzApp API endpoint is reachable.

  • Error messages:

    • Errors related to authorization usually indicate problems with the API key; recheck credentials.
    • Validation errors may occur if the Contact Id is malformed or does not exist.
    • Unexpected API responses might require checking the CrunchzApp service status or reviewing request payloads.

Links and References

Discussion