automate-whatsapp
Automate WhatsApp Workflows with Kapso
WhatsApp automation changes can be hard to coordinate across triggers, workflows, functions, and data. This skill gives structured Kapso workflow steps and command references for agent-assisted updates.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "automate-whatsapp" from https://skillstore.io/skills/sickn33-automate-whatsapp.md and its manifest at https://skillstore.io/api/skills/sickn33-automate-whatsapp/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "automate-whatsapp". Inspect the latest failed execution for my WhatsApp support workflow.
Expected outcome:
The workflow has one recent failed execution. The failure occurred after the routing step because the expected customer tier value was missing. Recommended next step: inspect the context path and confirm whether the table lookup returned a row.
Using "automate-whatsapp". Add an inbound WhatsApp trigger to workflow 123.
Expected outcome:
I found the available WhatsApp phone numbers and prepared the trigger details for workflow 123. This will create a new inbound trigger, so I will wait for your explicit approval before running the create step.
Using "automate-whatsapp". Review my graph update before deployment.
Expected outcome:
The updated graph keeps the original node IDs, adds one decision branch, and preserves the existing start node. Validation should run before update, and the final update needs the current lock version.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown backticks around commands, filenames, and field names rather than executable backtick syntax. The real concern is workflow safety: the skill documents destructive Kapso and WhatsApp automation actions without explicit confirmation guardrails.
Confirmed security concerns (1)
Risk Factors
โ๏ธ External commands (104)
๐ Network access (1)
๐ Env variables (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-automate-whatsapp/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-automate-whatsapp?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-automate-whatsapp?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-automate-whatsapp/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-automate-whatsapp.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). automate-whatsapp security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-automate-whatsapp/audits/4BibTeX citation
@techreport{sickn33-sickn33-automate-whatsapp-2026,
author = {sickn33},
title = {automate-whatsapp security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-automate-whatsapp/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "automate-whatsapp security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/sickn33-automate-whatsapp/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-automate-whatsapp:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Build Inbound Support Automation
Create and adjust a WhatsApp workflow that receives messages, routes users, and starts support handling.
Debug Conversation Failures
Inspect recent executions, read context values, and review event history to find broken workflow steps.
Connect Apps and Data
Configure action integrations, deploy workflow functions, and use database rows for workflow state.
Try These Prompts
List my Kapso workflows and identify the one that handles inbound WhatsApp support. Summarize the likely workflow purpose before suggesting changes.
Find the WhatsApp phone number ID for this account, then prepare an inbound message trigger for workflow WORKFLOW_ID. Ask for my confirmation before creating it.
Fetch workflow WORKFLOW_ID, explain its current graph, add a decision branch for VIP customers, validate the graph, and ask before updating it with the lock version.
Design a WhatsApp support workflow that checks a D1 table, calls an app action through an agent node, and deploys a helper function. Show each planned mutation before execution.
Best Practices
- Confirm every production create, update, delete, deploy, force, resume, or database mutation before execution.
- Keep API keys in environment variables and avoid placing secret values in prompts or workflow notes.
- Fetch the latest graph, preserve node IDs, validate changes, and re-fetch after every update.
Avoid
- Do not paste KAPSO_API_KEY or OAuth secrets into chat messages.
- Do not change existing node IDs or skip lock version checks during graph updates.
- Do not run delete, deploy, force status, resume, or row mutation commands without explicit approval.