Overview
This node enables logging into the Zalo messaging platform using a QR code. It generates a QR code image that users scan with their Zalo mobile app to authenticate. Upon successful login, it saves the authentication information into credentials for subsequent API requests.
Common scenarios include:
- Automating interactions with Zalo accounts without manual password entry.
- Integrating Zalo messaging features into workflows by authenticating via QR code.
- Securely storing and reusing Zalo session credentials in n8n.
Practical example:
- A workflow that sends notifications through Zalo after authenticating via this node’s QR code login.
Properties
| Name | Meaning |
|---|---|
| Proxy | HTTP proxy URL (e.g., https://user:pass@host:port) to route Zalo API requests through. |
Output
The node outputs an array of items, each containing:
json:success: Boolean indicating if the QR code was generated successfully.message: Confirmation message ("QR code generated successfully").fileName: The filename of the QR code image.credentialFilePath: Path where the credential file is saved.
binary:data: The QR code image data in PNG format, ready for use or download.
If an error occurs during execution, the output JSON contains an error field with the error message.
Dependencies
- Requires an API key credential for Zalo API authentication.
- Uses a Zalo client library internally to handle QR code login and session management.
- Optionally supports routing requests through an HTTP proxy specified by the user.
- Saves credential files locally on the n8n host machine.
Troubleshooting
Common issues:
- Failure to generate or display the QR code image due to network or proxy misconfiguration.
- Timeout waiting for QR code scan and login confirmation.
- Invalid or missing API authentication credentials.
Error messages:
- Errors related to login timeout indicate the QR code was not scanned in time; retry the operation.
- Proxy connection errors suggest incorrect proxy URL or unreachable proxy server.
- Credential-related errors mean the required API key credential is missing or invalid.
To resolve:
- Verify proxy settings if used.
- Ensure the API key credential is correctly configured.
- Scan the QR code promptly within the allowed timeframe.