2.6k
GitHub Stars
23
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill bazhuayu-webhook- _meta.json466 B
- bazhuayu-webhook.py17.9 KB
- CHANGES-v2.0.md3.7 KB
- config.example.json784 B
- MANUAL_SETUP.md2.6 KB
- MANUAL.md10.9 KB
- migrate-to-env.sh4.4 KB
- package.json2.4 KB
- QUICKSTART.md3.9 KB
- README.md7.6 KB
- RELEASE-2.0.1.md2.5 KB
- RELEASE-2.0.2.md2.9 KB
- RELEASE-2.0.3.md1.6 KB
- RELEASE-2.0.4.md2.7 KB
- RELEASE-v1.0.1.md2.5 KB
- RELEASE-v2.0.md2.7 KB
- run_daily.sh703 B
- SECURITY.md3.5 KB
- setup-secure.sh5.7 KB
- SKILL.md7.6 KB
- USAGE_EXAMPLE.md2.7 KB
- WEBHOOK_SETUP_PREVIEW.html10.7 KB
- WEBHOOK_SETUP.md3.6 KB
Overview
This skill triggers Bazhuayu (Octopus) RPA flows via webhook and supports passing custom parameters and secure signature generation. It centralizes webhook URL and key handling, prefers environment variables for secrets, and includes a secure setup and validation workflow. The tool is designed for CLI use with test, run, config and security-check commands.
How this skill works
The script reads webhook URL, signature key, and optional default parameters from config.json or environment variables, then computes the required HMAC-SHA256 signature and timestamp. It sends a properly signed POST to the Bazhuayu webhook endpoint with parameter payloads, and returns the API response (success batch IDs or structured error). Built-in commands allow dry-run testing and automated security checks before sending.
When to use it
- Automate triggering of Bazhuayu RPA flows from CI/CD pipelines or cron jobs
- Pass dynamic parameters to RPA tasks without modifying the RPA application
- Run safe, signed webhook calls when secrets must not be embedded in code
- Validate webhook configuration and signature behavior with a test mode
- Migrate older config files to environment-variable based secret management
Best practices
- Store BAZHUAYU_WEBHOOK_URL and BAZHUAYU_WEBHOOK_KEY in your shell profile or secrets manager, not in plaintext config files
- Prefer environment variables (higher priority) and use provided migrate-to-env.sh when upgrading
- Run secure-check before production runs to detect timestamp or key issues
- Use test mode to validate payload and signature without triggering real runs
- Restrict config.json file permissions to owner-only (script enforces 600)
Example use cases
- Trigger data extraction workflows nightly with parameterized date ranges from cron
- Invoke a scraping flow from CI after deployment to validate front-end changes
- Pass runtime parameters (A, B, etc.) from a monitoring or orchestration system to alter RPA behavior
- Use test command in staging to confirm signature and timestamp handling before production execution
- Migrate legacy config to environment variables and perform one-click secure setup with setup-secure.sh
FAQ
Set BAZHUAYU_WEBHOOK_URL and BAZHUAYU_WEBHOOK_KEY. Optional BAZHUAYU_PARAM_* variables override default params.
Why signature verification fails?
Common causes are incorrect key or system clock skew. Run secure-check and ensure system time is accurate and the key matches the environment value.
How do I test without sending a real request?
Use the test command which simulates signature generation and shows the prepared payload without calling the webhook.