Actions22
- Chat Actions
- Channel Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to stop the typing indicator status for a specified contact. It is useful in messaging automation workflows where you want to programmatically signal that the user or bot has stopped typing a message to a particular contact. For example, after sending a message or when cancelling a message draft, this node can be used to update the contact's UI by stopping the typing animation.
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 for the specified contact. This typically includes confirmation of the action or any error messages returned by the API. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating with the CrunchzApp API.
- The node sends requests to the CrunchzApp API endpoint at
https://api.crunchz.app/api. - Proper configuration of the API credential within n8n is necessary for successful operation.
Troubleshooting
- Invalid Contact Id: If the contact ID is malformed or does not exist, the API may return an error. 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 and active.
- Network Issues: Connectivity problems to the CrunchzApp API endpoint can cause request failures. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests might trigger rate limiting. Review API usage policies and implement retry logic if needed.
Links and References
- CrunchzApp API Documentation (assumed URL based on baseURL)
- n8n Documentation on Creating Custom Nodes