whapi icon

whapi

Use whapi channel services

Actions3

Overview

The node provides functionality to check the existence or status of a contact based on a phone number. It is useful in scenarios where you need to verify if a particular phone number is registered or active within a system before proceeding with further actions, such as sending messages or managing contacts.

For example, before sending a marketing message, you might want to confirm that the recipient's phone number is valid and reachable.

Properties

Name Meaning
Authentication Method of authentication; currently supports "Access Token" option.
Contact The phone number to check for validity or presence. This is a required string input.

Output

The output will contain JSON data representing the result of the contact check operation. This typically includes information about whether the contact exists, its status, or related metadata returned by the external service.

If the node supports binary data output (not evident from the provided code), it would represent associated media or files linked to the contact, but this is not indicated here.

Dependencies

  • Requires an API key or access token credential for authentication.
  • Depends on an external service accessible via the router module (./actions/router) which handles the actual contact checking logic.
  • The node uses shared descriptions and versioning info from ./actions/common.descriptions.

Troubleshooting

  • Invalid or missing phone number: Ensure the "Contact" property is provided and formatted correctly as a phone number.
  • Authentication errors: Verify that the access token or API key is valid and has the necessary permissions.
  • Network or API errors: Check connectivity to the external service and ensure the service endpoint is operational.
  • Unexpected response format: If the external service changes its API, the node may fail to parse the response correctly.

Links and References

  • No direct links available from the source code.
  • Refer to the external service’s API documentation for details on contact verification endpoints and authentication requirements.

Discussion