ZuckZapGo AI icon

ZuckZapGo AI

Send WhatsApp messages using ZuckZapGo - optimized for AI workflows
Join our community

Actions21

Overview

The "Check User" operation of the ZuckZapGo AI node verifies whether a given phone number has an active WhatsApp account. This is useful to validate recipients before attempting to send messages, thereby preventing errors related to invalid or inactive WhatsApp users.

Typical use cases include:

  • Pre-validating contact lists before bulk messaging campaigns.
  • Filtering out non-WhatsApp numbers in customer databases.
  • Ensuring message delivery attempts are made only to valid WhatsApp accounts.

For example, before sending promotional messages, you can use this operation to check if each phone number is registered on WhatsApp, avoiding unnecessary API calls and improving workflow efficiency.

Properties

Name Meaning
Phone Number (userPhone) The phone number to check, in international format without the "+" sign (e.g., 5491155553934).
Optimize Response Whether to optimize the API response to reduce token usage and improve AI processing.
Max Response Length Maximum number of characters in the response; longer responses will be truncated.
Include Only Essential Fields Whether to include only essential fields in the response to reduce noise.
Response Format How to format the response for optimal AI agent understanding. Options:
- Optimized: Clean, structured response optimized for AI processing
- Raw: Complete raw response from the API
- Summary: Brief summary with key information only

Output

The output JSON contains the response from the WhatsApp API indicating the existence status of the specified user(s). The structure typically includes:

  • data: An array with details about the checked phone numbers, including whether they have an active WhatsApp account.
  • If response optimization is enabled, the data may be truncated or simplified to reduce size and focus on essential information.
  • When saving avatars or media (not applicable here), binary data would be included, but for "Check User," output is purely JSON.

Example simplified output snippet:

{
  "data": [
    {
      "phone": "5491155553934@s.whatsapp.net",
      "exists": true
    }
  ],
  "_aiOptimized": true,
  "_truncated": {
    "originalCount": 1,
    "returnedCount": 1,
    "reason": "Optimized for AI processing"
  }
}

Dependencies

  • Requires an API key credential for authenticating with the ZuckZapGo WhatsApp API service.
  • The node uses HTTP requests to the ZuckZapGo API endpoints.
  • No additional environment variables are explicitly required beyond the API credential.
  • The node depends on internal helper functions for preparing media data and making authenticated API requests.

Troubleshooting

  • Error: Binary property not found — Not applicable for "Check User" but common in media operations when expected binary data is missing. Ensure the binary property name matches the input data.
  • Unknown operation error — Occurs if an unsupported operation value is set. Verify that "checkUser" is selected correctly.
  • API request failures — Could be due to invalid API credentials, network issues, or rate limits. Check API key validity and network connectivity.
  • Empty or unexpected response — May happen if the phone number format is incorrect. Ensure the phone number is in international format without "+" and properly formatted.
  • Continue On Fail option allows the node to proceed with other items even if one fails, useful in batch processing.

Links and References

  • ZuckZapGo GitHub Repository — Official source and documentation for the API used by this node.
  • WhatsApp Business API documentation (general reference for WhatsApp messaging concepts).

This summary focuses exclusively on the "Check User" operation of the ZuckZapGo AI node as requested.

Discussion