uazapi-groups

Fetch WhatsApp group names and JIDs from UazAPI into a JSON file.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Moisesjr20/gueclaw --skill uazapi-groups
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uazapi-groups
Source: https://github.com/Moisesjr20/gueclaw/tree/main/.agents/skills/uazapi-groups
Command: npx skills add https://github.com/Moisesjr20/gueclaw --skill uazapi-groups

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates retrieving WhatsApp group metadata from UazAPI and persisting a compact list of group names and JIDs to the agent's local data store, avoiding large API payloads that would overwhelm the LLM context.

Core Features & Use Cases

  • Group discovery and sync: Fetches all groups and stores name and JID in a normalized JSON file for fast lookup.
  • Server-side filtering for safety: Instructs trimming of the large API response on the VPS before loading into the agent to prevent token/context overflow.
  • Configurable and reproducible: Uses UAIZAPI_BASE_URL and UAIZAPI_TOKEN from environment variables and supports execution via vps_execute_command or api_request as directed.
  • Use case: Keep a nightly synchronized list of groups so the agent can answer queries like "what is the JID for 'Family Silva'?" without re-fetching full participant data.

Quick Start

Ask the agent to list and save all WhatsApp groups using the configured UAIZAPI token so it writes the compact groups.json file to the skill data path.

Frequently Asked Questions about uazapi-groups

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve and store WhatsApp group JIDs and names from UazAPI?

Retrieve and store WhatsApp group JIDs and names by running a curl request via vps_execute_command with the UAIZAPI token, then filtering the response server-side and saving a compact JSON file to the skill data path.

Why does fetching WhatsApp group metadata via API cause context overflow?

Fetching WhatsApp group metadata via API causes context overflow because full participant lists create large payloads. Server-side filtering trims the response to only group names and JIDs before loading into the agent.

Can I sync WhatsApp group lists using environment variables for UazAPI?

Yes, you can sync WhatsApp group lists using the UAIZAPI_BASE_URL and UAIZAPI_TOKEN environment variables to authenticate the API request and persist the normalized group data locally.

What is the best way to look up a WhatsApp group JID without re-fetching participant data?

The best way to look up a WhatsApp group JID is querying a locally persisted compact JSON file containing group names and JIDs, which is synchronized nightly to avoid re-fetching full participant data.

Does UazAPI group sync work with api_request instead of vps_execute_command?

Yes, UazAPI group sync works with api_request as an alternative execution method, provided the response is trimmed before writing the resulting JSON to .agents/skills/uazapi-groups/data/groups.json.

When should I not use full API payloads for WhatsApp group automation?

You should not use full API payloads for WhatsApp group automation when the response includes full participant lists, as this overwhelms the LLM context and causes token overflow during downstream processing.