npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@anhnt224/n8n-nodes-zalo

v0.1.1

Published

n8n community nodes for Zalo personal-account automation via unofficial Zalo Web API.

Downloads

80

Readme

n8n-nodes-zalo

Readable n8n community package for Zalo personal-account automation through zca-js.

Disclaimer: this package drives the unofficial Zalo Web API via zca-js. It can violate Zalo's Terms of Service and may get accounts flagged, rate-limited, or banned. Use at your own risk on accounts you control.

Features

  • Login with Zalo cookie.
  • Experimental login with Zalo QR.
  • Save login result as an n8n zaloUserApi credential by calling the n8n Public API.
  • Validate session and fetch account/user information.
  • List groups, get group metadata, and get group members.
  • Fetch group chat history.
  • Trigger workflows on new Zalo messages.

Security Defaults

The package intentionally does not include license checks, premium gates, telemetry, obfuscation, custom servers, or workflow mutation.

Defaults:

  • checkUpdate=false
  • logging=false
  • includeRaw=false
  • includeSensitiveData=false

Sensitive values are redacted from normal outputs and errors:

  • cookies
  • IMEI
  • full user agent
  • phone numbers
  • n8n API keys
  • Zalo secrets

Credentials

Zalo User API

Internal name: zaloUserApi

Fields:

  • cookie
  • imei
  • userAgent
  • language
  • checkUpdate
  • logging

n8n Public API

Internal name: n8nApi

Used only by Zalo Auth when Save as Credential is enabled.

Fields:

  • baseUrl
  • apiKey

Nodes

Zalo Auth

Operations:

  • Login With Cookie
  • Login With QR
  • Validate Credential

QR login emits the generated QR image to the n8n UI while the node is running. After the phone confirms login, the node saves the returned cookie and IMEI as a zaloUserApi credential when Save as Credential is enabled.

When saving credentials, the node creates one standalone zaloUserApi credential through POST /api/v1/credentials. It does not modify existing workflows or auto-attach credentials to nodes.

Zalo Account

Operations:

  • Validate Session
  • Get Me
  • Get User Info
  • Get Context

Zalo Group

Operations:

  • Get All Groups
  • Get Group Info
  • Get Group Members

Zalo Message

Operations:

  • Get Group Chat History

Zalo Trigger

Events:

  • New Message

Filters:

  • Thread type: all, direct, group
  • Include self messages
  • Include raw payload

Only one Zalo Web listener can run per account. Opening Zalo Web elsewhere can disconnect the listener. The trigger does not auto-reconnect; fix the session and reactivate the workflow.

Development

npm install
npm run build
npm test
npm pack --dry-run

Manual Test Checklist

  • Valid cookie creates a zaloUserApi credential.
  • Invalid cookie returns a login error without logging cookie data.
  • Missing IMEI returns ZALO_MISSING_CREDENTIAL_FIELD.
  • Created credential can be selected manually in Account/Group/Message/Trigger nodes.
  • Group history normalizes text and attachment messages without crashing.
  • Trigger emits direct and group messages and stops on workflow deactivation.

Notes

This package depends on [email protected] and Node.js 18+. n8n Public API credential creation can vary by n8n version and deployment plan.