Zender icon

Zender

Interact with Zender WhatsApp API

Overview

The "Get QR Info" operation of the Account resource in this node interacts with the Zender WhatsApp API to retrieve information about a WhatsApp account after it has been linked via a QR code. This is useful for confirming the status and details of the WhatsApp account associated with a given QR code token.

Typical use cases include:

  • Verifying that a WhatsApp account has been successfully linked.
  • Retrieving metadata or status information about the linked WhatsApp account.
  • Automating workflows that depend on the account linkage confirmation step.

For example, after generating a WhatsApp QR code for linking an account, you can use this operation by providing the token string from the QR code to fetch the account info and proceed accordingly.

Properties

Name Meaning
Token The token string obtained from creating a WhatsApp QR code. Used to query account info.

Output

The output JSON contains the response from the Zender WhatsApp API endpoint /get/wa.info queried with the provided token. It typically includes details about the WhatsApp account linked to that token, such as account status, identifiers, or other metadata returned by the API.

No binary data is output by this operation.

Example output structure (simplified):

{
  "accountId": "string",
  "status": "string",
  "linkedAt": "timestamp",
  "details": { /* additional account info */ }
}

Dependencies

  • Requires an API key credential for authenticating with the Zender WhatsApp API.
  • The node uses the base URL and secret API key configured in the credentials.
  • No additional environment variables are required beyond the API credential setup.

Troubleshooting

  • Invalid or expired token: If the token provided is invalid or expired, the API may return an error or empty response. Ensure the token is freshly obtained from the QR code creation step.
  • Authentication errors: Make sure the API key credential is correctly configured and active.
  • Network issues: Verify connectivity to the Zender API endpoint.
  • Unexpected API responses: Check if the API service is operational and review any error messages returned in the JSON output.

If the node throws an error, enabling "Continue On Fail" can help process multiple items without stopping the entire workflow.

Links and References

Discussion