Actions22
- Channel Actions
- Chat Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
The node interacts with the CrunchzApp API to mark a specific message as "seen." This operation is useful in messaging workflows where you want to update the status of messages programmatically, for example, to acknowledge that a message has been read by a user or system. Practical applications include automating customer support systems, chatbots, or any integration where message state tracking is necessary.
Properties
| Name | Meaning |
|---|---|
| Message Id | The ID of the message to mark as seen |
Output
The node outputs JSON data representing the response from the CrunchzApp API after marking the message as seen. This typically includes confirmation of the action and possibly updated message metadata. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the CrunchzApp API.
- The node sends requests to the base URL:
https://api.crunchz.app/api. - Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing message ID will cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent communication with the CrunchzApp API.
Error messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Message not found" errors suggest the provided message ID does not exist; double-check the ID.
- Timeout or network errors require checking internet connection and API availability.
Links and References
- CrunchzApp API Documentation (assumed based on base URL)
- n8n documentation on API Credentials