ZuckZapGo User icon

ZuckZapGo User

Get user information and manage presence with ZuckZapGo WhatsApp API

Overview

The node "ZuckZapGo User" integrates with the ZuckZapGo WhatsApp API to retrieve and manage user-related information and presence status on WhatsApp. It supports multiple operations such as checking if users have WhatsApp, fetching avatars, getting business profiles, managing presence, and more.

A common use case is automating WhatsApp user verification by checking if phone numbers or local IDs (LIDs) are registered on WhatsApp. Another practical example is retrieving user avatars or business profiles for contact enrichment in CRM systems. The node can also update the current user's status or push name, making it useful for automated presence management.

Properties

Name Meaning
Phone Numbers/LIDs Comma-separated list of phone numbers or Local IDs (LIDs) with @lid suffix to check for WhatsApp users. Example: 5491155553934,5491155553935,5491155554335@lid

Note: This property is required and shown only for the "Check Users" and "Get User Info" operations.

Output

  • The output JSON contains the response data from the ZuckZapGo WhatsApp API corresponding to the selected operation.
  • For the "Check Users" operation, the output includes information about whether each provided phone number or LID has WhatsApp.
  • If the operation involves fetching avatars and the option to save as binary is enabled, the avatar image is saved as binary data under a specified binary property name. The binary data includes:
    • Base64-encoded image data
    • MIME type (e.g., image/jpeg)
    • File extension and file name derived from the MIME type and phone number
  • For other operations, the output JSON structure varies according to the API response but generally contains user details, presence status, privacy settings, or mappings.

Dependencies

  • Requires an API key credential for authenticating requests to the ZuckZapGo WhatsApp API.
  • The node uses internal helper functions to validate phone numbers and make HTTP requests to the API endpoints.
  • No additional external dependencies beyond the configured API credential are needed.

Troubleshooting

  • Invalid phone number format: The node validates phone numbers before sending requests. Ensure phone numbers are in the correct international format without spaces or special characters.
  • API authentication errors: Make sure the API key credential is correctly configured and has sufficient permissions.
  • Empty or malformed responses: Verify that the phone numbers or LIDs exist and are correctly formatted. Also, check network connectivity to the API service.
  • Binary data issues: When saving avatars as binary, ensure the binary property name is set and that the returned avatar URL or data URI is valid.
  • Continue on Fail: If enabled, the node will continue processing remaining items even if one fails, returning error messages in the output JSON.

Links and References

Discussion