Overview
The Wuzapi User node interacts with the Wuzapi WhatsApp API to retrieve and manage user information and presence status. It supports multiple operations such as checking if users have WhatsApp, fetching detailed user info, retrieving avatars, getting contacts, and setting global presence.
This node is useful in scenarios where you want to automate WhatsApp user data retrieval or manage presence programmatically. For example:
- Verifying a list of phone numbers to see which ones are registered on WhatsApp.
- Fetching profile pictures of specific users for display or processing.
- Managing your WhatsApp presence status (online/offline) from an automation workflow.
- Retrieving all contacts associated with the authenticated WhatsApp account.
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 node outputs JSON data corresponding to the selected operation:
- Check Users / Get User Info: Returns an array of user objects with details about each phone number queried.
- Get Avatar: Returns avatar data including a URL or base64 image data. If "Save as Binary" is enabled, the avatar image is saved as binary data under the specified binary property name.
- Get Contacts: Returns a list of contacts associated with the WhatsApp account.
- Set Presence: Returns confirmation of the presence status update.
When saving avatars as binary, the binary data includes:
data: Base64 encoded image contentmimeType: Image MIME type (e.g., image/jpeg)fileExtension: File extension derived from MIME typefileName: Generated file name based on phone number and extension
Dependencies
- Requires connection to the Wuzapi WhatsApp API via an API key credential configured in n8n.
- Uses internal helper functions for phone number validation and API requests.
- No additional external dependencies beyond the configured API credential.
Troubleshooting
- Invalid phone number format: Ensure phone numbers are provided in international format without spaces or special characters. The node validates and trims input but malformed numbers may cause errors.
- API request failures: Errors returned by the Wuzapi API (e.g., authentication issues, rate limits) will be surfaced. Verify that the API key credential is valid and has necessary permissions.
- Avatar download issues: If saving avatar as binary, ensure the returned data is a valid base64 string. If the avatar URL starts with "http", use an HTTP Request node to download the image separately.
- Empty results: If no users are found or no contacts exist, the output JSON array may be empty.
Links and References
- Wuzapi WhatsApp API Documentation (example link, replace with actual if available)
- n8n documentation on Creating Custom Nodes
- n8n documentation on Working with Binary Data