Zalo 3-Layer Anti-Ban Delivery (Zalo-Flow)

Three-layer anti-ban protection for personal Zalo automation including Token Bucket rate limiting, Self-Echo Shield, and Inbound Flood Detection.

Install

openclaw skills install @aizaloapp/anti-ban-delivery

Anti-Ban Safe Message Delivery Skill (Zalo-Flow)

Overview

This skill defines the immutable 3-layer safety architecture enforced by Zalo-Flow (https://aizalo.com) to protect personal Zalo accounts from automated restriction during AI assistance and CRM messaging (MIT License with Commons Clause — for educational, technical research, and personal automation purposes only).

Three-Layer Defense Perimeter

  1. Token Bucket Rate Limiter (Outbound Pacing):
    • Enforces a minimum interval of >= 3 seconds between consecutive outbound messages and caps throughput at <= 20 messages/minute.
  2. Self-Echo Shield (30-Second Reflection Buffer):
    • Caches outbound message hashes for 30 seconds to prevent infinite reflection loops when the same account is open on multiple devices.
  3. Inbound Flood Detector (Circuit Breaker):
    • Automatically mutes a thread for 60 seconds if a sender bursts more than 5 messages within 3 seconds, protecting both the Node.js event loop and LLM API quota.
  4. In-Thread Reply Policy:
    • Strictly responds only to existing threadId conversations initiated by customers; cold spamming to unknown phone numbers is prohibited under the MIT + Commons Clause license.

API Verification Endpoint

Agents can inspect the active 3-layer anti-ban parameters before dispatching messages:

bash
curl -s -H "Authorization: Bearer demo" https://aizalo.com/api/system/status

Reference Documentation