automate-whatsapp

gokapso/agent-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/gokapso/agent-skills --skill automate-whatsapp
0 commentsdiscussion
summary

Build and manage WhatsApp automations with workflow graphs, triggers, functions, and integrations.

  • Create and edit workflow graphs with nodes and edges, manage triggers (inbound messages, API calls), and deploy custom functions for dynamic logic
  • Execute workflows with full context access (variables, system data, channel metadata) and debug executions via logs and event inspection
  • Integrate third-party apps and actions into agent nodes, query and manipulate D1 databases for persistent
skill.md

Automate WhatsApp

When to use

Use this skill to build and run WhatsApp automations: workflow CRUD, graph edits, triggers, executions, function management, app integrations, and D1 database operations.

Setup

Preferred path:

  • Kapso CLI installed and authenticated (kapso login)
  • Use the CLI for project/number discovery before wiring triggers or automations

Fallback path: Env vars:

  • KAPSO_API_BASE_URL (host only, no /platform/v1)
  • KAPSO_API_KEY

How to

Discover phone numbers first

Preferred path:

  1. Check project state: kapso status
  2. List connected numbers: kapso whatsapp numbers list --output json
  3. Resolve a display number when needed: kapso whatsapp numbers resolve --phone-number "<display-number>" --output json

Fallback path:

  1. List number configs for triggers: node scripts/list-whatsapp-phone-numbers.js

Edit a workflow graph

  1. Fetch graph: node scripts/get-graph.js <workflow_id> (note the lock_version)
  2. Edit the JSON (see graph rules below)
  3. Validate: node scripts/validate-graph.js --definition-file <path>
  4. Update: node scripts/update-graph.js <workflow_id> --expected-lock-version <n> --definition-file <path>
  5. Re-fetch to confirm

For small edits, use edit-graph.js with --old-file and --new-file instead.

If you get a lock_version conflict: re-fetch, re-apply changes, retry with new lock_version.

Manage triggers

  1. List: node scripts/list-triggers.js <workflow_id>
  2. Create: node scripts/create-trigger.js <workflow_id> --trigger-type <type> --phone-number-id <id>
  3. Toggle: node scripts/update-trigger.js --trigger-id <id> --active true|false
  4. Delete: node scripts/delete-trigger.js --trigger-id <id>

For inbound_message triggers, prefer kapso whatsapp numbers resolve --phone-number "<display-number>" --output json to get the exact phone_number_id. Fall back to node scripts/list-whatsapp-phone-numbers.js when the CLI is unavailable.

Debug executions

  1. List: node scripts/list-executions.js <workflow_id>
  2. Inspect: node scripts/get-execution.js <execution-id>
  3. Get value: node scripts/get-context-value.js <execution-id> --variable-path vars.foo
  4. Events: node scripts/list-execution-events.js <execution-id>

Create and deploy a function

  1. Write code with handler signature (see function rules below)
  2. Create: node scripts/create-function.js --name <name> --code-file <path>
  3. Deploy: node scripts/deploy-function.js --function-id <id>
  4. Verify: node scripts/get-function.js --function-id <id>

Set up agent node with app integrations

  1. Find model: node scripts/list-provider-models.js
  2. Find account: node scripts/list-accounts.js --app-slug <slug> (use pipedream_account_id)
  3. Find action: node scripts/search-actions.js --query <word> --app-slug <slug> (action_id = key)
  4. Create integration: node scripts/create-integration.js --action-id <id> --app-slug <slug> --account-id <id> --configured-props <json>
  5. Add tools to agent node via flow_agent_app_integration_tools

Database CRUD

  1. List tables: node scripts/list-tables.js
  2. Query: node scripts/query-rows.js --table <name> --filters <json>
  3. Create/update/delete with row scripts

Graph rules

  • Exactly one start node with id = start
  • Never change existing node IDs
  • Use {node_type}_{timestamp_ms} for new node IDs
  • Non-decide nodes have 0 or 1 outgoing next edge
  • Decide edge labels must match conditions[].label
  • Edge keys are source/target/label (not from/to)

For full schema details, see references/graph-contract.md.

Function rules

async function handler(request, env) {
  // Parse input
  const body = await request.json();
  // Use env.KV and env.DB as needed
  return new Response(JSON.stringify({ result: "ok" }));
}
  • Do NOT use export, export default, or arrow functions
  • Return a Response object

Execution context

Always use this structure:

  • vars - user-defined variables
  • system - system variables
  • context - channel data
  • metadata - request metadata

Scripts

Workflows

Script Purpose
list-workflows.js List workflows (metadata only)
get-workflow.js Get workflow metadata
create-workflow.js Create a workflow
update-workflow-settings.js Update workflow settings

Graph

Script Purpose
get-graph.js Get workflow graph + lock_version
edit-graph.js Patch graph via string replacement
update-graph.js Replace entire graph
validate-graph.js Validate graph structure locally

Triggers

Script Purpose
list-triggers.js List triggers for a workflow
create-trigger.js Create a trigger
update-trigger.js Enable/disable a trigger
delete-trigger.js Delete a trigger
list-whatsapp-phone-numbers.js List phone numbers for trigger setup

Executions

Script Purpose
list-executions.js List executions
get-execution.js Get execution details
get-context-value.js Read value from execution context
update-execution-status.js Force execution state
resume-execution.js Resume waiting execution
list-execution-events.js List execution events

Functions

Script Purpose
list-functions.js List project functions
get-function.js Get function details + code
create-function.js Create a function
update-function.js Update function code
deploy-function.js Deploy function to runtime
invoke-function.js Invoke function with payload
list-function-invocations.js List function invocations

App integrations

Script Purpose
list-apps.js Search integration apps
search-actions.js Search actions (action_id = key)
get-action-schema.js Get action JSON schema
list-accounts.js List connected accounts
create-connect-token.js Create OAuth connect link
configure-prop.js Resolve remote_options for a prop
reload-props.js Reload dynamic props
list-integrations.js List saved integrations
create-integration.js Create an integration
update-integration.js Update an integration
delete-integration.js Delete an integration

Databases

Script Purpose
list-tables.js List D1 tables
get-table.js Get table schema + sample rows
query-rows.js Query rows with filters
create-row.js Create a row
update-row.js Update rows
upsert-row.js Upsert a row
delete-row.js Delete rows

OpenAPI

Script Purpose
openapi-explore.mjs Explore OpenAPI (search/op/schema/where)

Install deps (once):

npm i

Examples:

node scripts/openapi-explore.mjs --spec workflows search "variables"
node scripts/openapi-explore.mjs --spec workflows op getWorkflowVariables
node scripts/openapi-explore.mjs --spec platform op queryDatabaseRows

Notes

  • Prefer file paths over inline JSON (--definition-file, --code-file)
  • action_id is the same as key from search-actions
  • --account-id uses pipedream_account_id from list-accounts
  • Variable CRUD (variables-set.js, variables-delete.js) is blocked - Platform API doesn't support it
  • Raw SQL execution is not supported via Platform API

References

Read before editing:

Other references:

Assets

File Description
workflow-linear.json Minimal linear workflow
workflow-decision.json Minimal branching workflow
workflow-agent-simple.json Minimal agent workflow
workflow-customer-support-intake-agent.json Customer support intake
workflow-interactive-buttons-decide-function.json Interactive buttons + decide (function)
workflow-interactive-buttons-decide-ai.json Interactive buttons + decide (AI)
workflow-api-template-wait-agent.json API trigger + template + agent
function-decide-route-interactive-buttons.json Function for button routing
agent-app-integration-example.json Agent node with app integrations

Related skills

  • integrate-whatsapp - Onboarding, webhooks, messaging, templates, flows
  • observe-whatsapp - Debugging, logs, health checks
[automate-whatsapp file map]|root: .
|.:{package.json,SKILL.md}
|assets:{agent-app-integration-example.json,databases-example.json,function-decide-route-interactive-buttons.json,functions-example.json,workflow-agent-simple.json,workflow-api-template-wait-agent.json,workflow-customer-support-intake-agent.json,workflow-decision.json,workflow-interactive-buttons-decide-ai.json,workflow-interactive-buttons-decide-function.json,workflow-linear.json}
|references:{app-integrations.md,databases-reference.md,execution-context.md,function-contracts.md,functions-payloads.md,functions-reference.md,graph-contract.md,node-types.md,triggers.md,workflow-overview.md,workflow-reference.md}
|scripts:{configure-prop.js,create-connect-token.js,create-function.js,create-integration.js,create-row.js,create-trigger.js,create-workflow.js,delete-integration.js,delete-row.js,delete-trigger.js,deploy-function.js,edit-graph.js,get-action-schema.js,get-context-value.js,get-execution-event.js,get-execution.js,get-function.js,get-graph.js,get-table.js,get-workflow.js,invoke-function.js,list-accounts.js,list-apps.js,list-execution-events.js,list-executions.js,list-function-invocations.js,list-functions.js,list-integrations.js,list-provider-models.js,list-tables.js,list-triggers.js,list-whatsapp-phone-numbers.js,list-workflows.js,openapi-explore.mjs,query-rows.js,reload-props.js,resume-execution.js,search-actions.js,update-execution-status.js,update-function.js,update-graph.js,update-integration.js,update-row.js,update-trigger.js,update-workflow-settings.js,upsert-row.js,validate-graph.js,variables-delete.js,variables-list.js,variables-set.js}
|scripts/lib/databases:{args.js,filters.js,kapso-api.js}
|scripts/lib/functions:{args.js,kapso-api.js}
|scripts/lib/workflows:{args.js,kapso-api.js,result.js}
how to use automate-whatsapp

How to use automate-whatsapp on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add automate-whatsapp
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/gokapso/agent-skills --skill automate-whatsapp

The skills CLI fetches automate-whatsapp from GitHub repository gokapso/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/automate-whatsapp

Reload or restart Cursor to activate automate-whatsapp. Access the skill through slash commands (e.g., /automate-whatsapp) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.857 reviews
  • Arjun Shah· Dec 28, 2024

    automate-whatsapp is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ama Gonzalez· Dec 24, 2024

    Keeps context tight: automate-whatsapp is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Neel Haddad· Dec 24, 2024

    I recommend automate-whatsapp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Olivia Sethi· Dec 24, 2024

    Useful defaults in automate-whatsapp — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Dec 16, 2024

    Keeps context tight: automate-whatsapp is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Soo Gonzalez· Dec 16, 2024

    automate-whatsapp reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ganesh Mohane· Dec 8, 2024

    automate-whatsapp reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sakshi Patil· Nov 27, 2024

    I recommend automate-whatsapp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Naina Choi· Nov 15, 2024

    automate-whatsapp reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Omar Malhotra· Nov 15, 2024

    Registry listing for automate-whatsapp matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 57

1 / 6