GOWA icon

GOWA

Interact with Go WhatsApp Web MultiDevice API

Overview

This node integrates with the Go WhatsApp Web MultiDevice API, enabling users to interact with WhatsApp programmatically. Specifically, for the User resource and the Check Contact operation, it allows checking information about a WhatsApp contact by phone number. This is useful in scenarios where you want to verify if a phone number corresponds to a valid WhatsApp user or retrieve basic info about that contact.

Practical examples include:

  • Validating user phone numbers before sending messages.
  • Fetching contact details to personalize communication.
  • Automating workflows that depend on user presence or status on WhatsApp.

Properties

Name Meaning
User Phone Phone number to get info for. If left empty, the node retrieves info for the authenticated user's own account.

Output

The output is a JSON object containing the contact information retrieved from the Go WhatsApp Web MultiDevice API. The exact structure depends on the API response but typically includes fields such as contact existence, profile name, status, and possibly avatar or other metadata.

If the node supports binary data (not explicitly shown here), it would likely relate to media such as avatars or profile pictures, but this is not detailed in the provided code.

Dependencies

  • Requires an API key credential for authenticating with the Go WhatsApp Web MultiDevice API.
  • The node expects a base URL configured via credentials to connect to the API endpoint.
  • No additional external dependencies are indicated beyond the API service.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an incorrectly formatted phone number may result in errors or no data returned.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • "Unknown resource: ..." — indicates an invalid resource parameter; ensure "user" is selected.
    • Errors related to API responses will be passed through; check the error message for details.
  • Resolutions:

    • Verify API credentials and host URL configuration.
    • Ensure phone numbers are in the correct international format.
    • Use the "continue on fail" option to handle errors gracefully in workflows.

Links and References

Discussion