N8N Tools - Uazapi icon

N8N Tools - Uazapi

Complete Uazapi integration - Premium WhatsApp API with advanced messaging and automation

Overview

This node integrates with the Uazapi WhatsApp API to manage WhatsApp groups, specifically allowing you to remove participants from a group. It is useful in scenarios where you need to automate group management tasks such as moderating group membership by removing unwanted or inactive participants.

For example, if you run a community or customer support group on WhatsApp and want to automatically remove users who violate rules or no longer belong to the group, this node can be used within an n8n workflow to perform that action programmatically.

Properties

Name Meaning
Group ID The unique identifier of the WhatsApp group from which participants will be removed.
Participants Comma-separated phone numbers of participants to remove (e.g., 5511999999999,5511888888888).
Additional Fields Optional extra parameters:
• Reply to Message ID: ID of message to reply to
• Delay (seconds): Delay before sending the request
• Disable Link Preview: Whether to disable link previews
• Mention Users: Comma-separated phone numbers to mention

Output

The node outputs JSON data representing the response from the Uazapi WhatsApp API after attempting to remove the specified participants from the group. This typically includes status information about the operation's success or failure.

If the operation fails for any participant or due to other reasons, the output JSON will contain error details.

No binary data is produced by this operation.

Dependencies

  • Requires an active Uazapi WhatsApp API account.
  • Needs an API key credential, API token, instance ID, and API base URL configured in n8n credentials.
  • The node sends requests through a proxy endpoint at https://n8ntools.io/api/v1/proxy/uazapi using the provided API key for authentication.

Troubleshooting

  • Common issues:

    • Invalid or missing Group ID or participant phone numbers will cause errors.
    • Incorrect formatting of participant phone numbers (should be comma-separated without spaces).
    • Insufficient permissions or invalid API tokens may result in authorization errors.
    • Network or proxy issues could prevent successful API calls.
  • Error messages:

    • Errors returned from the API are included in the output JSON under an error field.
    • If the node throws an error, verify that all required fields are correctly set and credentials are valid.
    • To continue processing other items despite errors, enable "Continue On Fail" in the node settings.

Links and References

Discussion