WSAPI icon

WSAPI

Interact with WSAPI WhatsApp API

Actions50

Overview

This node integrates with the WSAPI WhatsApp API to retrieve detailed information about a specific WhatsApp contact. It is particularly useful for workflows that need to fetch contact details such as profile information or status based on the unique WhatsApp contact identifier (phone number with country code appended by @s.whatsapp.net). For example, it can be used in customer support automation to pull up contact info before responding or in marketing workflows to verify contact data.

Properties

Name Meaning
Contact ID The unique WhatsApp contact identifier formatted as phone number with country code + @s.whatsapp.net (e.g., 1234567890@s.whatsapp.net). This is required to specify which contact to retrieve.
Cache Results Boolean option to enable caching of the contact data for repeated requests with the same Contact ID, improving performance and reducing API calls.
Cache TTL (sec) Time-to-live in seconds for how long the cached contact data should be stored when caching is enabled. Minimum value is 1 second. Default is 300 seconds.

Output

The node outputs JSON data representing the retrieved contact information from the WhatsApp API. This typically includes fields such as the contact's profile details, status, and other metadata provided by the API. If binary data were involved (e.g., contact picture), it would be summarized accordingly, but this operation focuses on JSON contact data.

Dependencies

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

Troubleshooting

  • Invalid Contact ID Format: Ensure the Contact ID follows the format phoneNumber@s.whatsapp.net including the country code without spaces or special characters.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Cache Not Updating: If caching is enabled but data seems stale, check the Cache TTL setting and adjust as needed.
  • Operation Not Implemented Error: This error indicates the selected operation is not supported; ensure "Get Contact" is chosen under the "Contact" resource.
  • Resource Not Known Error: Occurs if an unsupported resource is selected; confirm the resource is set to "Contact".

Links and References

Discussion