ZuckZapGo User icon

ZuckZapGo User

Get user information and manage presence with ZuckZapGo WhatsApp API
Join our community

Actions9

Overview

This node integrates with the ZuckZapGo WhatsApp API to retrieve user-related information and manage presence. Specifically, the Get Avatar operation fetches the profile picture (avatar) of a specified WhatsApp user, group, newsletter, or local ID (LID). It supports retrieving either a thumbnail preview or the full image and optionally saving the avatar as binary data within the workflow.

Common scenarios for this node include:

  • Displaying user avatars in customer support dashboards.
  • Archiving or processing profile pictures for marketing or CRM purposes.
  • Automating retrieval of group or newsletter avatars for content management.

Example: You want to get the profile picture of a WhatsApp contact by their phone number or group ID and use it in your workflow, either as a URL or as binary data for further processing.

Properties

Name Meaning
Target Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to get avatar for
Preview Whether to get a thumbnail preview (true) or the full picture (false)
Save as Binary Whether to save the avatar image as binary data within the workflow
Binary Property Name The name of the binary property where the avatar will be stored if "Save as Binary" is enabled

Output

The output JSON contains the response from the ZuckZapGo API's /user/avatar endpoint. Typically, this includes:

  • URL: A string URL pointing to the avatar image (thumbnail or full size).
  • Alternatively, a data URI string containing the image encoded in base64.

If Save as Binary is enabled and the avatar data is a base64 data URI, the node extracts the image data and stores it in the specified binary property with appropriate MIME type and file extension. This allows downstream nodes to process the avatar image directly as binary data.

If the avatar URL starts with "http", the node adds a note suggesting to use an HTTP Request node to download the image.

Dependencies

  • Requires an active connection to the ZuckZapGo WhatsApp API via an API key credential configured in n8n.
  • The node uses internal helper functions to validate phone numbers and make authenticated API requests.
  • No additional external dependencies beyond the configured API access.

Troubleshooting

  • Invalid Target Format: Ensure the target value is a valid phone number, group ID, newsletter ID, or LID. Phone numbers are validated and must be properly formatted.
  • Avatar Not Found: If the API returns no avatar data, verify that the target exists and has a profile picture set.
  • Binary Data Issues: When saving as binary, ensure the binary property name is unique and does not conflict with other binary data in the workflow.
  • HTTP URL Handling: If the avatar URL is an HTTP link, remember to add an HTTP Request node to download the image; the node itself does not download images from URLs.
  • API Errors: Common API errors may relate to authentication failures or rate limits. Check your API key and usage quotas.

Links and References

Discussion