Overview
The Wuzapi User node interacts with the Wuzapi WhatsApp API to retrieve and manage user-related information. It supports operations such as checking if phone numbers have WhatsApp accounts, fetching detailed user info, retrieving avatars, getting contacts, and setting global presence status.
This node is useful in scenarios where you want to verify WhatsApp users, gather profile data, or manage presence programmatically. For example:
- Marketing automation workflows that validate customer phone numbers before sending messages.
- Customer support systems that fetch user avatars for display.
- Presence management to show availability status across multiple WhatsApp accounts.
Properties
| Name | Meaning |
|---|---|
| Operation | The action to perform. Options: Check Users, Get Avatar, Get Contacts, Get User Info, Set Presence |
| Phone Numbers | Comma-separated list of phone numbers to check or get info for (used in "Check Users" and "Get User Info" operations) |
| Phone Number | Single phone number to get avatar for (used in "Get Avatar" operation) |
| Preview | Whether to get a thumbnail (true) or full picture (false) for the avatar |
| Save as Binary | Whether to save the avatar image as binary data |
| Binary Property Name | Name of the binary property to store the avatar image (if saving as binary) |
| Presence Type | Global presence status to set. Options: Available (online), Unavailable (offline) |
Output
- The output JSON contains the response from the Wuzapi API corresponding to the selected operation.
- For "Check Users" and "Get User Info", the output includes arrays of user data keyed by phone numbers.
- For "Get Avatar", the output includes a URL or base64 data of the user's avatar image. If "Save as Binary" is enabled, the avatar image is saved as binary data under the specified binary property name.
- For "Get Contacts", the output lists all contacts retrieved.
- For "Set Presence", the output confirms the updated presence status.
- In case of errors, the output contains an error message object.
Dependencies
- Requires an API key credential for authenticating with the Wuzapi WhatsApp API.
- Uses internal helper functions for phone number validation and making HTTP requests to the Wuzapi API endpoints.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid phone number format: The node validates phone numbers; ensure they are correctly formatted international numbers without spaces or special characters.
- API request failures: Errors from the Wuzapi API (e.g., invalid credentials, rate limits) will be returned as error messages in the output. Verify API key validity and usage limits.
- Avatar download issues: When saving avatars as binary, ensure the binary property name is set and the avatar data is in a supported format (base64 or accessible URL).
- Empty results: If no users are found or contacts are empty, confirm the phone numbers exist on WhatsApp and the account has access rights.
Links and References
- Wuzapi WhatsApp API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes
- n8n documentation on Working with Binary Data