WSAPI icon

WSAPI

Interact with WSAPI WhatsApp API
Join our community

Actions50

Overview

This node integrates with the WSAPI WhatsApp API to retrieve information about WhatsApp users. Specifically, the "Get User" operation under the "User" resource fetches details about a WhatsApp user based on their phone number.

Common scenarios for this node include:

  • Verifying if a phone number is registered on WhatsApp.
  • Retrieving user profile information such as name or status.
  • Enriching contact data in workflows by fetching up-to-date WhatsApp user info.

Practical example:

  • A customer support workflow that receives a phone number and uses this node to get the user's WhatsApp profile before sending a personalized message.

Properties

Name Meaning
Phone Number The phone number of the WhatsApp user to get information about. Include country code without "+" symbol (e.g., "1234567890" for a US number). This is a required string input.

Output

The node outputs JSON data containing the retrieved WhatsApp user information. The exact structure depends on the WSAPI response but typically includes fields such as user ID, display name, profile picture URL, and possibly status or other metadata.

If the node supports binary data output (not explicitly shown here), it would represent media like profile pictures or other attachments related to the user.

Dependencies

  • Requires an API key credential for authenticating with the WSAPI WhatsApp API.
  • The base URL for the API must be configured in the node credentials.
  • No additional external dependencies are indicated beyond the WSAPI service.

Troubleshooting

  • Common issues:

    • Invalid or missing phone number format (must exclude "+" and include country code).
    • API authentication failures due to incorrect or expired credentials.
    • Network connectivity problems preventing access to the WSAPI endpoint.
    • The specified user may not exist or be registered on WhatsApp, resulting in empty or error responses.

  • Error messages:

    • "The resource "users" is not known!" — indicates an invalid resource selection; ensure "User" resource is selected.
    • "The operation "get" is not implemented yet!" — suggests the operation is not supported; verify correct operation choice.
    • API errors returned from WSAPI will be surfaced; check credentials and phone number validity.

To resolve errors:

  • Double-check the phone number format.
  • Verify API credentials and base URL configuration.
  • Ensure the WSAPI service is reachable and operational.

Links and References

Discussion