AU

automate-whatsapp

Builds and manages WhatsApp automation workflows, triggers, and state integrations using the Kapso platform.

Install

mkdir -p .claude/skills/automate-whatsapp-saminrules && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13876" && unzip -o skill.zip -d .claude/skills/automate-whatsapp-saminrules && rm skill.zip

Installs to .claude/skills/automate-whatsapp-saminrules

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automatin...
200 chars✓ has a “when” trigger
Advanced

Key capabilities

  • Edit WhatsApp workflow graphs
  • Manage WhatsApp triggers
  • Debug WhatsApp workflow executions
  • Create and deploy custom functions
  • Set up agent nodes with app integrations
  • Perform database CRUD operations

How it works

The skill uses Node.js scripts to interact with the Kapso platform API, allowing for CRUD operations on workflows, triggers, functions, and database records for WhatsApp automations.

Inputs & outputs

You give it
Workflow ID, trigger type, function code, or database query
You get back
Updated workflow graph, managed triggers, execution details, deployed function, or database results

When to use automate-whatsapp

  • Edit a WhatsApp automation workflow
  • Configure a new trigger
  • Inspect execution history
  • Manage workflow integrations

About this skill

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

Env vars:

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

How to

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, first run node scripts/list-whatsapp-phone-numbers.js to get phone_number_id.

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

ScriptPurpose
list-workflows.jsList workflows (metadata only)
get-workflow.jsGet workflow metadata
create-workflow.jsCreate a workflow
update-workflow-settings.jsUpdate workflow settings

Graph

ScriptPurpose
get-graph.jsGet workflow graph + lock_version
edit-graph.jsPatch graph via string replacement
update-graph.jsReplace entire graph
validate-graph.jsValidate graph structure locally

Triggers

ScriptPurpose
list-triggers.jsList triggers for a workflow
create-trigger.jsCreate a trigger
update-trigger.jsEnable/disable a trigger
delete-trigger.jsDelete a trigger
list-whatsapp-phone-numbers.jsList phone numbers for trigger setup

Executions

ScriptPurpose
list-executions.jsList executions
get-execution.jsGet execution details
get-context-value.jsRead value from execution context
update-execution-status.jsForce execution state
resume-execution.jsResume waiting execution
list-execution-events.jsList execution events

Functions

ScriptPurpose
list-functions.jsList project functions
get-function.jsGet function details + code
create-function.jsCreate a function
update-function.jsUpdate function code
deploy-function.jsDeploy function to runtime
invoke-function.jsInvoke function with payload
list-function-invocations.jsList function invocations

App integrations

ScriptPurpose
list-apps.jsSearch integration apps
search-actions.jsSearch actions (action_id = key)
get-action-schema.jsGet action JSON schema
list-accounts.jsList connected accounts
create-connect-token.jsCreate OAuth connect link
configure-prop.jsResolve remote_options for a prop
reload-props.jsReload dynamic props
list-integrations.jsList saved integrations
create-integration.jsCreate an integration
update-integration.jsUpdate an integration
delete-integration.jsDelete an integration

Databases

ScriptPurpose
list-tables.jsList D1 tables
get-table.jsGet table schema + sample rows
query-rows.jsQuery rows with filters
create-row.jsCreate a row
update-row.jsUpdate rows
upsert-row.jsUpsert a row
delete-row.jsDelete rows

OpenAPI

ScriptPurpose
openapi-explore.mjsExplore 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:

  • references/graph-contract.md - Graph schema, computed vs editable fields, lock_version
  • references/node-types.md - Node types and config shapes
  • references/workflow-overview.md - Execution flow and states

Other references:

  • references/execution-context.md - Context structure and variable substitution
  • references/triggers.md - Trigger types and setup
  • references/app-integrations.md - App integration and variable_definitions
  • references/functions-reference.md - Function management
  • references/functions-payloads.md - Payload shapes for functions
  • references/databases-reference.md - Database operations

Assets

FileDescription
workflow-linear.jsonMinimal linear workflow
workflow-decision.jsonMinimal branching workflow
workflow-agent-simple.jsonMinimal agent workflow
workflow-customer-support-intake-agent.jsonCustomer support intake
workflow-interactive-buttons-decide-function.jsonInteractive buttons + decide (function)
workflow-interactive-buttons-decide-ai.jsonInteractive buttons + decide (AI)
workflow-api-template-wait-agent.jsonAPI trigger + template + agent
function-decide-route-interactive-buttons.jsonFunction for button routing
agent-app-integration-example.jsonAgent node with app integrations

Related skills

  • integrate-whatsapp - Onboarding, webhooks, messaging, templates, flows
  • observe-whatsapp - Debugging, logs, health checks
<!-- FILEMAP:BEGIN -->
[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-

---

*Content truncated.*

When not to use it

  • When KAPSO_API_BASE_URL environment variable is not set
  • When KAPSO_API_KEY environment variable is not set

Prerequisites

KAPSO_API_BASE_URLKAPSO_API_KEY

Limitations

  • The skill requires `KAPSO_API_BASE_URL` and `KAPSO_API_KEY` environment variables.
  • Workflow graph edits require fetching the `lock_version` and handling conflicts.
  • Custom functions must follow a specific handler signature and return a `Response` object.

How it compares

This skill provides a programmatic interface for building and managing WhatsApp automations, offering detailed control over workflow graphs, triggers, and functions, unlike a purely UI-driven approach.

Compared to similar skills

automate-whatsapp side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
automate-whatsapp (this skill)05moReviewAdvanced
telegram-bot-builder1066moReviewIntermediate
mcp-integration219moReviewIntermediate
n8n-workflow-patterns162moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

mcp-integration

anthropics

This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.

21123

n8n-workflow-patterns

czlonkowski

Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.

16115

n8n-code-javascript

czlonkowski

Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.

7122

n8n-expression-syntax

czlonkowski

Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.

6111

n8n-node-configuration

czlonkowski

Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node_essentials and get_node_info, or learning common configuration patterns by node type.

7108

Search skills

Search the agent skills registry