--- name: automate-whatsapp version: 1.0.0 category: 开发编程 trigger_words: tags: platform: coze source: DeepseekModel source_url: https://deepseekmodel.com/skill?id=gokapso-agent-skills-skills-automate-whatsapp-skill-md --- name automate-whatsapp description Build and debug Kapso WhatsApp workflows, triggers, functions, and executions. Automate WhatsApp When to use Use this skill to build and run WhatsApp automations: workflow CRUD, graph edits, WhatsApp and Project Event triggers, Project Event emissions, executions, function management, webhook tools, and MCP tools. Setup Preferred path: Kapso CLI installed and authenticated ( kapso login ) For workflow and function edits, use source-controlled projects with kapso link , kapso pull , kapso build , and kapso push For workflow code, use @kapso/workflows and export a Workflow instance from workflow.js or workflow.ts Fallback path: Env vars: KAPSO_API_BASE_URL (host only, no /platform/v1 ) KAPSO_API_KEY How to Edit workflows locally Use this path first when the user is working in, or can create, a local repo. npm install -g @kapso/cli npm install --save-dev @kapso/workflows kapso login kapso link --project kapso pull Edit workflows//workflow.js or workflow.ts with @kapso/workflows : import { START , Workflow } from "@kapso/workflows" ; const workflow = new Workflow ( "inbound-support" , { name : "Inbound Support" , status : "draft" , }); workflow. addTrigger ({ type : "inbound_message" , phoneNumberId : "" , }); workflow. addNode ( START , { position : { x : 100 , y : 100 }, }); workflow. addNode ( "reply" , { type : "send_text" , message : "Thanks for reaching out." , }); workflow. addEdge ( START , "reply" ); export default workflow; Build and push: kapso build kapso push --dry-run kapso push workflow Use kapso push to push every local function and workflow. See references/local-workflow-source.md for repo layout, source-file behavior, and JSON-only editing. Discover phone numbers first Preferred path: Check project state: kapso status List connected numbers: kapso whatsapp numbers list --output json Resolve a display number when needed: kapso whatsapp numbers resolve --phone-number "" --output json Fallback path: List number configs for triggers: node scripts/list-whatsapp-phone-numbers.js Edit a workflow graph through API scripts Prefer local source sync for workflow edits. Use these scripts as a fallback for debugging, direct graph inspection, or API-only environments. Fetch graph: node scripts/get-graph.js (note the lock_version ) Edit the JSON (see graph rules below) Validate: node scripts/validate-graph.js --definition-file Update: node scripts/update-graph.js --expected-lock-version --definition-file 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 List: node scripts/list-triggers.js Create: node scripts/create-trigger.js --trigger-type --phone-number-id Toggle: node scripts/update-trigger.js --trigger-id --active true|false Delete: node scripts/delete-trigger.js --trigger-id For inbound_message triggers, prefer kapso whatsapp numbers resolve --phone-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. For project_event triggers, register or update the Project Event definition first when the user is defining an event type/schema: node scripts/project-event-definitions.js create \ --name conversation.csat_scored \ --description "Customer satisfaction score for a conversation" \ --property-schema '{"score":{"type":"number"},"reason":{"type":"string"}}' Then create the trigger: node scripts/create-trigger.js \ --trigger-type project_event \ --triggerable-attributes '{"event_name":"conversation.csat_scored","property_key":"score","operator":"gte","property_value":4}' Definitions are metadata only. Do not emit a sample event just to register a name unless the user explicitly accepts that side effect. Manage Project Event definitions Use definitions for event names, descriptions, and flat scalar property schemas. Emitted events are separate records created by POST /platform/v1/events , emit_event nodes, Function node project_events , or Agent node emit_event . List: node scripts/project-event-definitions.js list Create/update by name: node scripts/project-event-definitions.js create --name [--description ] [--property-schema ] Update by ID: node scripts/project-event-definitions.js update --definition-id [--name ] [--description ] [--property-schema ] Build workflows with Project Events Use this checklist when a workflow needs to remember or react to durable business facts: Define the event first when the user is introducing a new event name or schema. Use project_event triggers when a workflow should react to an emitted event. Use an emit_event node for deterministic workflow-step emission. Use Function node project_events when emission depends on function code output. Use Agent node emit_event only when the agent should decide whether/when to record the fact. Enable the emit_event default tool and configure allowed event definitions before relying on it. Project-event-triggered workflows are observers and cannot emit Project Events. Do not add event emission to a workflow that starts from a Project Event trigger. Debug executions Search workflow logs first when you have an execution ID: kapso logs search --query "" --source flow_event --filter flow_execution_id= --period 7d --limit 20 --output json List: node scripts/list-executions.js Inspect: node scripts/get-execution.js Get value: node scripts/get-context-value.js --variable-path vars.foo Events: node scripts/list-execution-events.js Create and deploy a function Write code with handler signature (see function rules below) Create: node scripts/create-function.js --name --code-file [--public-endpoint true] Deploy: node scripts/deploy-function.js --function-id Verify: node scripts/get-function.js --function-id Use --public-endpoint true when the function should be callable without X-API-Key via the Kapso-hosted invoke URL. This is only supported for Cloudflare functions. New functions default to invoke_response_mode=passthrough , which returns the function body directly on successful invoke. Legacy wrapped functions can be migrated later with update-function.js . Set up agent node with remote sandbox repositories Use this when the agent needs a remote ephemeral workspace to inspect or modify repository files during a workflow run. Read references/agent-remote-sandbox.md for the execution model and field rules Find model: node scripts/list-provider-models.js Copy assets/agent-remote-sandbox-github-repo-example.json as a starting point, or edit the agent node under data.config Set sandbox_enabled: true Set sandbox_network_mode to allow_all or allow_list If using allow_list , add extra outbound hosts in sandbox_allowed_outbound_hosts Add GitHub repositories to flow_agent_resources with: resource_type: "github_repository" repo_url branch pat Write the system prompt so it explicitly reads from /workspace/repos/ before making changes Validate and update the graph Notes: Remote sandbox is beta and free during the beta sandbox_enabled controls whether the remote workspace and sandbox tools are available Repository resources stay configured even if sandbox access is turned off later v1 supports GitHub repositories only Use a repository root URL, not a GitHub file URL or tree/... URL Repositories are mounted into /workspace/repos/ inside the remote sandbox Use references/agent-remote-sandbox.md and references/node-types.md for the exact shape 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 secrets 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 Project Events Script Purpose project-event-definitions.js List, create, or update Project Event definitions 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, optionally with a public invoke endpoint update-function.js Update function code, public endpoint setting, or migrate a legacy wrapped function to passthrough deploy-function.js Deploy function to runtime invoke-function.js Invoke function with payload list-function-invocations.js List function invocations 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 Notes Prefer file paths over inline JSON ( --definition-file , --code-file ) Use observe-whatsapp for cross-source Logs search when debugging a workflow alongside API calls, Meta events, or webhook deliveries. Variable CRUD ( variables-set.js , variables-delete.js ) is blocked - Platform API doesn't support it References Read the references for the operation you are changing: references/local-workflow-source.md - Local workflow source edits and CLI sync references/graph-contract.md - Graph edits: schema, computed vs editable fields, and lock_version references/node-types.md - Adding or changing node configuration references/workflow-overview.md - Execution behavior, state changes, and resumption For function-only work, read the function references below; graph/source references are needed only if the workflow changes too. Other task-specific references: references/execution-context.md - Context structure and variable substitution references/triggers.md - Trigger types and setup references/agent-remote-sandbox.md - Remote sandbox behavior, repo resources, mounted paths references/functions-reference.md - Function management references/functions-payloads.md - Payload shapes for functions Assets | File | Description |