whatsapp-flows

Design WhatsApp Flows with server-backed validation and dynamic data.

Updated Oct 30, 2025
One-click install
npx skills add https://github.com/mberg/claude-skills --skill whatsapp-flows
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: whatsapp-flows
Source: https://github.com/mberg/claude-skills/tree/main/skills/whatsapp-flows
Command: npx skills add https://github.com/mberg/claude-skills --skill whatsapp-flows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoring WhatsApp Flows requires coordinating multi-screen conversations, data binding, and server integration patterns. This Skill provides a structured, documented approach to design, validate, and deploy flows efficiently and securely.

Core Features & Use Cases

  • Standardized screen definitions with id, title, layout, and consistent navigation
  • Server integration patterns including data_api_version and routing_model for back-end validation and dynamic data
  • Comprehensive guidance on data-binding, conditional logic (If/Switch), and global references for cross-screen state
  • Real-world use cases such as form collection, dynamic product lists, and server-validated workflows

Quick Start

Describe a WhatsApp Flow in the standard JSON format shown in the Skill documentation and run the provided validators to ensure it conforms to the schema.

Frequently Asked Questions about whatsapp-flows

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

FAQPage Schema
How do I design WhatsApp Flows with server-backed validation?▼

To build WhatsApp Flows with server integration, you define multi-screen navigation and data binding in a standard JSON format while configuring data_api_version and routing_model for back-end validation. The Skill provides templates and validators to enforce Business 3.0 API rules during implementation.

What is conditional routing in WhatsApp Flows and how does it work?▼

Conditional routing in WhatsApp Flows uses If and Switch logic combined with global references to control multi-screen navigation. This mechanism manages cross-screen state, allowing the conversation to dynamically adapt paths based on user input or server-validated data.

How do I bind dynamic data from a server in a WhatsApp Flow?▼

You bind dynamic server data in a WhatsApp Flow by configuring server integration patterns including data_api_version and routing_model. This connects your back-end validation logic to the screen definitions, enabling dynamic data population for use cases like dynamic product lists and server-validated workflows.

Does this approach to WhatsApp Flow design enforce the Business 3.0 API rules?▼

Yes, this approach to WhatsApp Flow design enforces Business 3.0 API rules by providing structured screen definitions and built-in validators. These validators check your standard JSON format against the required schema, ensuring your multi-screen navigation and server integration comply with API requirements.

What are the limitations of authoring WhatsApp Flows without server integration?▼

Authoring WhatsApp Flows without server integration limits you to static data and prevents back-end validation. Without configuring the routing_model and data_api_version, you cannot implement server-validated workflows, dynamic product lists, or conditional routing based on real-time cross-screen state.