ZaloLogin via QR Code icon

ZaloLogin via QR Code

ZaloLoginQrCode Trigger.

ZaloLogin via QR Code

AI-generated

Overview

This node implements a trigger for logging into Zalo (a popular Vietnamese messaging app) via a QR code. It initiates a login session that generates a QR code image, which users scan with their Zalo mobile app to authenticate. Once scanned and connected, the node captures session details such as cookies and user identifiers, enabling further automated interactions with Zalo's web API.

Common scenarios include:

  • Automating workflows that require authenticated access to Zalo accounts.
  • Monitoring or reacting to events in a Zalo account after successful login.
  • Integrating Zalo login into broader automation pipelines without manual intervention beyond scanning the QR code.

Practical example:

  • A marketing automation workflow triggers when a user logs into a Zalo account via QR code, then sends welcome messages or collects data from the account.

Properties

Name Meaning
Proxy Optional proxy URL to route requests through (e.g., http(s)://user:pass@host:port). Helps bypass blocks, limits, or multiple account restrictions by using Vietnamese IP addresses to avoid bans.

Output

The node outputs data when the QR code is generated and when the connection is established:

  • json: Contains a timestamp indicating when the QR code was generated.
  • binary.data: The QR code image encoded as a PNG file, ready for display or further processing.

After successful connection:

  • The node internally stores session credentials (cookies, user agent, IMEI) but does not output them directly. These are used to authenticate subsequent API calls.

Dependencies

  • Requires an API key credential for authentication with an external service (referred to generically as "an API key credential").
  • Uses a helper method to send authenticated HTTP requests to a base URL configured in the credentials.
  • Depends on a Zalo login library/module that handles QR code generation and event listening.
  • Optionally supports routing requests through a proxy server specified by the user.

Troubleshooting

  • No token given.: This message appears if the required API key credential or base URL is missing or invalid. Ensure the credential is properly configured.
  • QR code not appearing: Verify network connectivity and proxy settings if used. The QR code is generated asynchronously; delays may occur.
  • Connection never established: Could be due to scanning issues or expired QR codes. Retry the login process.
  • Proxy misconfiguration: Incorrect proxy URLs can block requests. Confirm the proxy string format and credentials.

Links and References

Discussion