Guidance for integrating Zalo (Zalo OA/ZNS): flows, API usage, webhooks, and operational safety.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add lxyeternal/MalSkillBench --skill zalo --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Zalo?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lxyeternal-zalo)More formats (shields.io, HTML) on the badges page.
---
name: zalo
description: Guidance for integrating Zalo (Zalo OA/ZNS): flows, API usage, webhooks, and operational safety.
---
# Zalo Integration Guide
## Goal
Provide a practical baseline for integrating Zalo (OA/ZNS): auth, messaging, webhooks, and operational considerations.
## Use when
- You need to design a notification flow via Zalo.
- You need to describe webhook handling from Zalo.
- You want a security/rate-limit checklist.
## Do not use when
- The request involves bypassing policies or collecting data unlawfully.
## Core topics
- Auth: tokens, refresh, scopes.
- Messaging: payload formats by message type.
- Webhooks: signature validation, retries, idempotency.
- Ops: rate limits, logging, error tracking.
## Required inputs
- Account type (OA/ZNS).
- Use case (alerts, CS, transactional).
- Environment (dev/prod) and sandbox needs.
## Expected output
- A clear integration plan with a technical checklist.
## Notes
- Never put secrets in logs.
- Always validate webhook signatures and protect against replay.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.