CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API

Actions22

Overview

This node interacts with the CrunchzApp API to stop the typing indicator status for a specified contact. In messaging applications, a typing indicator shows when a user is actively typing a message. This node allows you to programmatically stop that indicator for a given contact, which can be useful in scenarios where you want to control or reset the typing status remotely, such as in automated chatbots or customer support workflows.

Practical examples:

  • Automatically stopping the typing indicator if a chatbot finishes composing a message earlier than expected.
  • Resetting the typing status after a timeout or error condition in a messaging automation.
  • Managing user experience by controlling when typing indicators appear or disappear in multi-agent chat systems.

Properties

Name Meaning
Contact Id The unique identifier of the contact (in the format xxx@c.us) for whom to stop typing

Output

The node outputs JSON data representing the response from the CrunchzApp API after attempting to stop the typing indicator. This typically includes confirmation of the action's success or failure and any relevant metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the CrunchzApp API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://api.crunchz.app/api.
  • The node sends JSON-formatted requests and expects JSON responses.

Troubleshooting

  • Invalid Contact Id: If the provided contact ID is malformed or does not exist, the API may return an error indicating the contact was not found. Verify the contact ID format (xxx@c.us) and correctness.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or token is correctly set up in n8n credentials.
  • Network Issues: Connectivity problems to the CrunchzApp API endpoint can result in timeouts or unreachable errors. Check network access and API service status.
  • API Rate Limits: Excessive requests might trigger rate limiting. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion