Actions22
- Chat Actions
- Channel Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to mark a specific message as "seen." It is useful in scenarios where you want to programmatically update the status of messages, for example, to acknowledge that a message has been read or processed. This can help automate workflows involving message handling, such as customer support ticketing systems or chatbots that track message states.
A practical example would be automatically marking incoming messages as seen once they have been logged or responded to by another system.
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 operation's success and may contain 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 CrunchzApp API endpoint at
https://api.crunchz.app/api. - Proper configuration of the API key credential within n8n is necessary for successful operation.
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 and resolutions:
- "Unauthorized" or similar authentication errors: Verify that the API key credential is correctly configured and valid.
- "Message not found": Check that the provided Message Id exists and is correct.
- Timeouts or network errors: Ensure stable internet connection and that the CrunchzApp API service is reachable.
Links and References
- CrunchzApp API Documentation (assumed URL based on baseURL)
- n8n documentation on API Credentials