Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
The "Unstar Message" operation in the Message resource allows users to remove a star mark from a specific message. This is useful in messaging applications where starring messages helps highlight or bookmark important content, and un-starring removes that highlight when it is no longer needed.
Practical examples include:
- A user wants to clean up their starred messages list by un-starring messages they have already addressed.
- Automated workflows that manage message statuses, such as un-starring messages after processing them.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID (a numeric identifier for the node execution context) |
| Message Id | The unique identifier of the message to unstar. Example format: true_123456789@c.us_123ABC456DEF |
Output
The output JSON will typically contain the response from the API indicating the success or failure of the unstar action on the specified message. It may include confirmation details such as the message ID and status.
If the node supports binary data output, it would relate to any media or attachments associated with the message, but this operation primarily deals with metadata (starring status), so binary output is unlikely.
Dependencies
- Requires an API key credential for authenticating with the WaAPI service.
- The node interacts with the WaAPI endpoint at
https://waapi.app/api/v1. - Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or malformed Message Id: Ensure the message ID follows the expected format.
- Authentication errors: Verify that the API key credential is correctly set up and has the required permissions.
- Network or API downtime: Check connectivity and WaAPI service status.
Error messages:
- Unauthorized or 401 errors indicate invalid or missing API credentials.
- 404 Not Found may mean the message ID does not exist or is incorrect.
- 400 Bad Request could be due to missing required parameters like Message Id.
Resolving these usually involves verifying input parameters and API credentials.
Links and References
- WaAPI Documentation (for detailed API usage and message operations)
- n8n documentation on creating custom nodes