Zalo Health Check icon

Zalo Health Check

Validate a Zalo Web session and report cookie/session health

Zalo Health Check

AI-generated

Summary

Checks whether the configured Zalo Web session can log in, then returns account and cookie health details. When the check fails, the node either returns an error result or throws an n8n error according to the failure setting and workflow error handling.

Inputs

  • Fail Workflow When Unhealthy — Defaults to true. When false, returns { "ok": false, "checked_at": ..., "error": ... } instead of throwing if credentials or login fail. Continue On Fail also makes the node return this error result.
  • Zalo API credentials (required) — Requires a cookie, IMEI, and user agent; language defaults to vi, and a proxy can be supplied. Cookie input must be valid JSON or an object.

Output shape

One n8n item containing a JSON health report on success, or an error result when configured not to throw.

The success report includes ok: true, own_id, account, credential-presence flags, cookie expiration status, whether a refreshed cookie is available, and checked_at. Own ID, account info, or refreshed-cookie lookup failures are reported as null or false; they do not fail the check. Cookie health includes the cookie count, earliest expiration, seconds remaining, and an optional expiry warning.

Examples

Example 1: Health check succeeds

Provide valid Zalo API credentials. Fail Workflow When Unhealthy defaults to true and does not affect successful checks.

Example 2: Health check fails

With Fail Workflow When Unhealthy enabled, an unusable session or invalid credentials throw an n8n error unless Continue On Fail is enabled. Disable the setting to return an item with ok: false and the error message.

Links

Discussion