Wuzapi User icon

Wuzapi User

Get user information and manage presence with Wuzapi WhatsApp API

Overview

This node integrates with the Wuzapi WhatsApp API to manage user information and presence status. It allows users to check if phone numbers have WhatsApp accounts, retrieve avatars, get contact lists, fetch detailed user info, and set a global presence status (online or offline).

The Set Presence operation specifically sets the global presence status of the user associated with the API credentials. This is useful in scenarios where you want to programmatically control whether your WhatsApp presence appears as online or offline, for example:

  • Automatically setting presence to "unavailable" during non-working hours.
  • Indicating availability dynamically based on external triggers or workflows.

Properties

Name Meaning
Presence Type Global presence status to set. Options: "Available" (show as online), "Unavailable" (show as offline)

Output

The output is a JSON array containing the response from the Wuzapi API for the presence update request. The structure depends on the API's response but generally confirms the success or failure of the presence change.

No binary data is produced by the Set Presence operation.

Dependencies

  • Requires an active connection to the Wuzapi WhatsApp API via an API key credential.
  • The node uses an HTTP POST request to the /user/presence endpoint of the Wuzapi API.
  • Proper configuration of the API credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Network connectivity problems can prevent successful API calls.
    • Providing unsupported presence types (other than "available" or "unavailable") will likely result in errors.
  • Error messages:

    • Errors returned from the API are passed through; typical messages might include authentication errors or invalid parameter errors.
    • If the node fails and "Continue On Fail" is not enabled, the workflow execution will stop.
  • Resolution tips:

    • Verify that the API key credential is correctly configured and valid.
    • Ensure the presence type value is one of the allowed options.
    • Check network connectivity and API endpoint accessibility.

Links and References

Discussion