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 retrieve user information and manage presence-related data. Specifically, the "Get Phone From LID" operation allows users to obtain a phone number or JID (WhatsApp identifier) from a given Local ID (LID). This is useful in scenarios where you have an internal or local identifier for a WhatsApp user and need to resolve it back to their actual phone number or JID.

Practical examples include:

  • Converting stored LIDs in your system into usable phone numbers for messaging.
  • Synchronizing contact lists by resolving LIDs to phone numbers.
  • Automating workflows that require mapping between internal IDs and WhatsApp contacts.

Properties

Name Meaning
Local ID (LID) The Local ID string (e.g., 1234567890@lid.whatsapp.net) used to get the corresponding phone number or JID. This property is required for the "Get Phone From LID" operation.

Output

The output JSON contains the response from the ZuckZapGo API endpoint /user/lid/from-lid. It typically includes the phone number or JID associated with the provided LID.

The structure of the output JSON depends on the API response but generally will be an object or array containing the resolved phone number(s) or JID(s).

No binary data is produced by this operation.

Dependencies

  • Requires an active connection to the ZuckZapGo WhatsApp API.
  • Requires an API key credential configured in n8n to authenticate requests to the ZuckZapGo API.
  • The node uses the internal helper function zuckzapgoApiRequest to make HTTP requests to the API endpoints.

Troubleshooting

  • Invalid or missing LID: If the provided LID is malformed or does not exist, the API may return an error or empty result. Ensure the LID is correctly formatted and valid.
  • Authentication errors: If the API key credential is missing or invalid, requests will fail. Verify that the API key is correctly set up in n8n credentials.
  • Network issues: Connectivity problems can cause request failures. Check network access to the ZuckZapGo API endpoint.
  • API rate limits: Excessive requests might be throttled by the API. Review API usage limits and adjust workflow frequency accordingly.

Common error messages will typically come from the API response and should be handled by enabling "Continue On Fail" in the node settings to capture errors gracefully.

Links and References

Discussion