Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
The "Mute Chat" operation in the Chat resource allows users to mute a specific chat conversation. Muting a chat means that notifications or alerts from that chat will be silenced, which is useful when you want to avoid distractions from certain contacts or group chats. This node can mute a chat either indefinitely or until a specified date and time, after which the chat will automatically be unmuted.
Practical examples:
- Temporarily muting a noisy group chat during work hours.
- Muting a contact's chat indefinitely if you do not wish to receive notifications from them.
- Scheduling an automatic unmute for a chat after a vacation period ends.
Properties
| Name | Meaning |
|---|---|
| Id | Instance ID representing the specific instance of the service or connection being used. |
| Chat Id | The unique identifier of the chat to mute. Format: <countrycode><usernumber>@c.us for individual chats or @g.us for groups. Example: 50664083362@c.us. |
| Unmute Date | Optional ISO 8601 formatted date-time string specifying when the chat should be automatically unmuted. If omitted, the chat remains muted indefinitely. Example: 2024-12-31T23:59:59.999Z. |
Output
The node outputs JSON data reflecting the result of the mute operation. This typically includes confirmation details such as the chat ID muted and the status of the mute action. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the WaAPI service.
- The node interacts with the WaAPI API endpoint at
https://waapi.app/api/v1. - Proper configuration of the API key credential within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing chat ID format may cause the operation to fail.
- Incorrect or expired API credentials will prevent the node from authenticating with the external service.
- Providing an improperly formatted unmute date (not ISO 8601) might lead to errors or unexpected behavior.
Error messages and resolutions:
- Authentication errors: Verify that the API key credential is correctly set up and has not expired.
- Invalid chat ID: Ensure the chat ID follows the required format (
<countrycode><usernumber>@c.usor@g.us). - Date parsing errors: Confirm that the unmute date is a valid ISO 8601 string.
Links and References
- ISO 8601 Date and Time Format
- WaAPI Official Documentation (for more details on API usage and chat management)