ZuckZapGo User icon

ZuckZapGo User

Get user information and manage presence with ZuckZapGo WhatsApp API
Join our community

Actions9

Overview

This node integrates with the ZuckZapGo WhatsApp API to manage user information and presence status on WhatsApp. It supports multiple operations such as checking if users have WhatsApp, retrieving avatars, getting business profiles, managing contacts, and setting global presence status.

The Set Presence operation specifically allows you to set your global WhatsApp presence status as either "Available" (online) or "Unavailable" (offline). This can be useful in automation workflows where you want to programmatically control your visibility or availability on WhatsApp based on external triggers or conditions.

Practical examples:

  • Automatically set your WhatsApp presence to "Unavailable" during non-working hours.
  • Change presence to "Available" when a support ticket is assigned to you.
  • Integrate with calendar events to toggle presence status dynamically.

Properties

Name Meaning
Presence Type Global presence status to set. Options:
- Available: Show as online
- Unavailable: Show as offline

Output

The node outputs JSON data reflecting the response from the ZuckZapGo WhatsApp API for the presence update request. The structure typically contains confirmation of the presence status change or any relevant metadata returned by the API.

No binary data output is associated with the Set Presence operation.

Dependencies

  • Requires an active connection to the ZuckZapGo WhatsApp API.
  • Requires an API key credential configured in n8n for authentication with the ZuckZapGo service.
  • The node uses internal helper functions to validate phone numbers and make authenticated HTTP requests to the API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Network connectivity problems may prevent successful API calls.
    • Providing unsupported presence types or malformed input parameters could result in API errors.

  • Error messages:

    • Errors returned from the API will be propagated, often indicating invalid parameters or authorization issues.
    • If the node is set to continue on fail, error details will be included in the output JSON under an error field.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Ensure the presence type value is one of the supported options ("available" or "unavailable").
    • Check network connectivity and API endpoint accessibility.

Links and References

Discussion