Habilidades automate-whatsapp
📦

automate-whatsapp

Riesgo bajo ⚙️ Comandos externos🌐 Acceso a red🔑 Variables de entorno

Automate WhatsApp Messaging Workflows

Build sophisticated WhatsApp automations without manual coding. Configure workflow triggers, manage executions, and integrate with external services through the Kapso platform.

Soporta: Claude Codex Code(CC)
🥉 73 Bronce
1

Descargar el ZIP de la skill

2

Subir en Claude

Ve a Configuración → Capacidades → Skills → Subir skill

3

Activa y empieza a usar

Pruébalo

Usando "automate-whatsapp". List all WhatsApp triggers for workflow wf_123

Resultado esperado:

Found 2 triggers: (1) inbound_message trigger for +1-555-0100 (active), (2) inbound_message trigger for +1-555-0101 (inactive)

Usando "automate-whatsapp". Show execution events for exec_456

Resultado esperado:

Execution started at 10:30 AM -> Message node executed -> Wait node started -> User responded at 10:35 AM -> Decide node evaluated -> End node completed

Usando "automate-whatsapp". Query customers table where status equals active

Resultado esperado:

Retrieved 15 rows matching filters. Sample: Customer ABC Corp (status: active, plan: premium), Customer XYZ Ltd (status: active, plan: standard)

Auditoría de seguridad

Riesgo bajo
v1 • 2/24/2026

Static analysis flagged 137 patterns in SKILL.md documentation file, but all are false positives. The detected 'external_commands' are markdown code examples showing Node.js script usage, not actual shell execution. Network and env_access flags reference documentation content (GitHub URL and configuration examples), not runtime behavior. No malicious intent detected - this is legitimate workflow automation documentation for the Kapso platform.

1
Archivos escaneados
258
Líneas analizadas
4
hallazgos
1
Auditorías totales
Problemas de riesgo bajo (1)
Documentation References External Scripts
SKILL.md references Node.js scripts in scripts/ directory that were not included in the scan. While the documentation appears legitimate, the actual script implementations should be reviewed before production deployment.

Factores de riesgo

⚙️ Comandos externos (3)
🌐 Acceso a red (1)
🔑 Variables de entorno (1)
Auditado por: claude

Puntuación de calidad

38
Arquitectura
100
Mantenibilidad
87
Contenido
50
Comunidad
88
Seguridad
100
Cumplimiento de la especificación

Lo que puedes crear

Customer Support Automation

Build automated customer support flows that handle common inquiries, collect user information, and route complex cases to human agents via WhatsApp.

E-commerce Order Notifications

Create workflows that send order confirmations, shipping updates, and delivery notifications automatically when triggered by e-commerce platform events.

Interactive Survey Collection

Design interactive button-based surveys that collect customer feedback through WhatsApp with conditional branching based on responses.

Prueba estos prompts

Create Simple Notification Workflow
Create a WhatsApp workflow that sends a welcome message when a user first contacts the business. Include a start node and a message node with the welcome text.
Build Decision-Based Routing
Create a workflow with a decide node that routes users based on their message content. If message contains 'support', route to support team. If message contains 'sales', route to sales team. Otherwise, send a general inquiry response.
Integrate External API for Data Lookup
Build a workflow that looks up customer order status by phone number. Create a function node that queries the orders database, then send a personalized message with the order details to the customer.
Multi-Step Conversation with State Management
Create an interactive survey workflow using button nodes. Collect user responses across multiple messages, store answers in execution context variables, and generate a summary at the end. Handle timeout scenarios if user stops responding.

Mejores prácticas

  • Always fetch the workflow graph before editing to get the current lock_version and avoid conflicts
  • Use file paths for graph definitions and function code instead of inline JSON for better maintainability
  • Validate workflow graphs locally before submitting updates to catch structural errors early
  • Test trigger configurations in a development workflow before deploying to production phone numbers
  • Store sensitive credentials like API keys in environment variables, never in workflow definitions

Evitar

  • Changing existing node IDs in a workflow graph - this breaks execution history and references
  • Using export statements or arrow functions in function code - Kapso requires standard function handler syntax
  • Creating workflows with multiple start nodes - exactly one start node with id 'start' is required
  • Referencing variables without initializing them in the execution context first

Preguntas frecuentes

What do I need before using this skill?
You need a Kapso platform account, WhatsApp Business API access, and environment variables KAPSO_API_BASE_URL and KAPSO_API_KEY configured.
Can I modify workflow graphs while they have active executions?
Yes, but use the lock_version mechanism. Fetch the graph first, make changes, then update with the expected lock_version to prevent conflicts.
What programming languages work for custom functions?
Functions use JavaScript with a specific handler signature: async function handler(request, env). The code runs in Kapso's serverless runtime.
How do I connect to external services like Slack or Google Sheets?
Use app integrations. Search for the app, get the action_id, create an integration with OAuth credentials, then reference it in agent nodes.
Can I store data between workflow executions?
Yes, use D1 database tables for persistent storage or the KV store for simple key-value data accessible via env.KV and env.DB in functions.
What happens if a workflow execution fails?
Failed executions can be inspected using get-execution and list-execution-events scripts. You can resume certain executions or force status updates for debugging.

Detalles del desarrollador

Estructura de archivos

📄 SKILL.md