# automate-whatsapp

A skill for building and debugging Kapso WhatsApp automations: workflows, triggers, functions and execution tracing.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 4000 installs · ★ 190
- Author: gokapso
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/gokapso/agent-skills/tree/HEAD/skills/automate-whatsapp/SKILL.md
- Updated: 2026-10-09
- HTML: https://affpapa.org/en/nevibecode/skills/automate-whatsapp

## What it does

The skill walks an agent through Kapso work: creating and editing workflows, changing the graph, wiring inbound message and Project Event triggers, emitting events, reading executions, managing functions, webhook tools and MCP tools. It fits projects where the WhatsApp automation already runs on Kapso and you would rather change it from the editor than click through a web UI.

The preferred route is a local repo under source control. You need the Kapso CLI installed and authenticated (`kapso login`), then `kapso link` to bind the project, `kapso pull` to fetch, `kapso build` and `kapso push` to ship. Workflow code uses `@kapso/workflows`, with a `Workflow` instance exported from `workflow.js` or `workflow.ts`. A fallback exists through the `KAPSO_API_BASE_URL` and `KAPSO_API_KEY` environment variables.

Graph edits through the API scripts are a fallback for debugging or API-only setups, not the default. Watch `lock_version` there: on a conflict you re-fetch, re-apply and retry with the new value. One trap worth knowing before you plan the work — a workflow started by a Project Event trigger is an observer and cannot emit Project Events, so adding emission to it will not work.

Debugging runs through `kapso logs search` with an execution ID, then listing executions, reading context values and events. Functions are created by script and deployed as a separate step, and the public endpoint flag is supported for Cloudflare functions only.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add gokapso/agent-skills --skill automate-whatsapp -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/automate-whatsapp/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/automate-whatsapp/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add gokapso/agent-skills --skill automate-whatsapp -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/automate-whatsapp/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add gokapso/agent-skills --skill automate-whatsapp -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/automate-whatsapp/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install gokapso/agent-skills automate-whatsapp
```

2. **Manually: put the files in place**
- File: `.github/skills/automate-whatsapp/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add gokapso/agent-skills --skill automate-whatsapp -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/gokapso/agent-skills --path skills/automate-whatsapp
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/automate-whatsapp/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add gokapso/agent-skills --skill automate-whatsapp -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/gokapso/agent-skills/tree/HEAD/skills/automate-whatsapp/SKILL.md

## When to use it
- assemble a WhatsApp workflow from nodes and edges in a local repo
- attach an inbound message trigger to the right phone number
- register a Project Event and react to it from a workflow
- trace a failed execution by its ID and find the broken step
- create a function and deploy it to Kapso

## Example prompts
- Show me the graph for the inbound-support workflow and add a reply node
- Create an inbound_message trigger for this workflow using the project number
- Pull up this execution ID and tell me why it failed

## Similar
- [whatsapp](https://affpapa.org/en/nevibecode/skills/whatsapp.md) — skill · 368 installs
- [whatsapp-marketing](https://affpapa.org/en/nevibecode/skills/whatsapp-marketing.md) — skill · 1600 installs
- [twilio-whatsapp-send-message](https://affpapa.org/en/nevibecode/skills/twilio-whatsapp-send-message.md) — skill · 2 installs
- [loop-library](https://affpapa.org/en/nevibecode/skills/forward-future-loop-library.md) — skill · 2400 installs
- [n8n-subworkflows](https://affpapa.org/en/nevibecode/skills/n8n-subworkflows.md) — skill · 1900 installs

From the same set: [gokapso/agent-skills](https://affpapa.org/en/nevibecode/by/gokapso/agent-skills.md) — 3 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md