Actions37
- Message Actions
- Media Actions
- Contact Actions
- Group Actions
- Instance Actions
- Webhook Actions
Overview
This node integrates with a premium WhatsApp API service to manage WhatsApp groups and perform various group-related operations. Specifically, the "Leave Group" operation allows the authenticated WhatsApp instance to leave a specified WhatsApp group.
Common scenarios where this node is beneficial include automating group management tasks such as exiting groups when no longer needed, managing group memberships programmatically, or integrating WhatsApp group actions into broader automation workflows.
For example, you might use this node to automatically remove your WhatsApp instance from a group after a project ends or when certain conditions in your workflow are met.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the WhatsApp group to leave. |
| Additional Fields | Optional extra parameters: |
- Reply to Message ID: ID of a message to reply to (not typically used for leaving group).
- Delay (seconds): Delay before executing the leave action.
- Disable Link Preview: Whether to disable link previews in messages (not relevant here).
- Mention Users: Phone numbers to mention (comma-separated) (not relevant here). |
Output
The node outputs a JSON object containing the response from the WhatsApp API proxy server regarding the leave group request. This typically includes confirmation of the action or error details if the operation failed.
The output structure is:
{
"json": {
// Response data from the WhatsApp API about leaving the group
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data is produced by this operation.
Dependencies
Requires an active WhatsApp API instance configured with:
- An API key credential for authentication.
- API URL endpoint.
- API token for authorization.
- Instance ID representing the WhatsApp session.
The node sends requests through a proxy service hosted at
https://n8ntools.io/api/v1/proxy/uazapi.Proper credentials must be set up in n8n to authenticate with the WhatsApp API.
Troubleshooting
Common Issues:
- Invalid or missing Group ID will cause the operation to fail.
- Incorrect or expired API tokens or instance IDs will result in authentication errors.
- Network issues or proxy service downtime can prevent successful API calls.
Error Messages:
- Errors returned from the WhatsApp API will be included in the output JSON under an
errorfield if "Continue On Fail" is enabled. - Authentication failures typically indicate invalid API token or instance ID; verify credentials.
- "Unknown resource" errors indicate misconfiguration of the resource parameter.
- Errors returned from the WhatsApp API will be included in the output JSON under an
Resolution Tips:
- Double-check the Group ID format and ensure the WhatsApp instance is part of the group.
- Verify that all required credentials are correctly configured and valid.
- Enable "Continue On Fail" during testing to capture error details without stopping the workflow.
Links and References
- WhatsApp Business API Documentation
- n8n Documentation on Credentials
- Uazapi WhatsApp API Service (proxy service used by this node)