Identify a callback URL, create its subscription record, and optionally deliver the registration to a configured external service.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install event-callback-url-complete
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install event-callback-url-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Event Callback Planner?
Event Callback Planner is an executable Openclaw Skills workflow that turns a subscription_request into a callback_url, then uses that result to create or update a local business artifact representing the recorded callback. Its single runner handles both identification and downstream processing, returning a structured result for the complete workflow.
By default, the skill operates locally and contacts no external service. Configure SMTP or an HTTP delivery endpoint to perform the declared real-world action and receive a delivery receipt reporting the outcome. This gives developers a clear distinction between local recordkeeping and explicitly configured external delivery.
Event Callback Planner Use Cases
- Process an incoming subscription request and identify its callback URL.
- Create or update a local callback registration record for a business workflow.
- Submit a callback registration to an HTTP endpoint when delivery is configured.
- Send a subscription-related message through SMTP when mail settings are provided.
- Run the workflow locally without external calls when testing or validating the business artifact.
How Event Callback Planner Works
- Read the upstream
subscription_requestfrom the input JSON file. - Run the identification stage to compute the
callback_url. - Pass the identification result to the downstream stage and compute
recorded_callback. - Create or update the
subscription_receipt_recordbeneath the explicitly supplied output directory. - If SMTP or HTTP delivery is configured through environment variables or a delivery-config file, perform the declared action and return a delivery receipt with an outcome such as
sent,delivered, orfailed. Otherwise, retain the record locally and report delivery as unconfigured.
Event Callback Planner Setup
Run the workflow with Python and provide an input file and output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
To provide optional delivery settings through a configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
For SMTP delivery, configure CLAWHUB_SMTP_HOST and, as needed, CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. Alternatively, supply an SMTP configuration containing smtp_host, smtp_port, and from_addr in the delivery-config file.
For HTTP registration or submission, set CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY, or provide an endpoint object in the delivery-config file. Delivery targets, credentials, and recipients must be provided explicitly at runtime. Without delivery configuration, the workflow remains local. Delivery errors produce a nonzero exit.
Event Callback Planner Data Schema & Taxonomy
Workflow data
| Stage | Input or result | Purpose |
|---|---|---|
| Upstream identification | subscription_request → callback_url |
Reads the request and identifies the callback address. |
| Downstream processing | Identification result → recorded_callback |
Computes the business result and creates or updates the local artifact. |
| Business effect | subscription_receipt_record |
Represents the registration or submission action. |
| Optional delivery | delivery receipt |
Reports the configured delivery outcome, such as sent, delivered, failed, or unconfigured. |
Files and configuration
examples/request.json— bundled upstream input.examples/expected.json— example of the complete two-stage output shape; runtime paths and receipt identifiers are excluded.scripts/upstream/— identification implementation:operation.py,validation.py, andconfig.json.scripts/downstream/— downstream delivery implementation, includingdeliver_effect.scripts/run.py— complete workflow runner.source-map.json— provenance information for both extracted stages.--output-dir— explicitly selected location for the local business artifact.--delivery-config— optional file-based delivery configuration.
Event Callback Planner Advanced Features
- Combines identification, downstream business processing, local artifact creation, and optional delivery in one executable workflow.
- Supports SMTP message delivery and HTTP registration or submission effects.
- Accepts delivery settings from runtime environment variables or an explicit configuration file.
- Uses local-only behavior by default, avoiding external calls when no delivery target is configured.
- Returns a delivery receipt when external delivery is configured and reports failures through a nonzero process exit.
- Includes separate upstream and downstream implementations plus a source map for stage provenance.
SKILL.md
Loading
Related Openclaw Skills
Account Report Recipe Planner
Turn a report request into a grouped account report, with optional real-world delivery and a receipt confirming the outcome.
Reconciliation Threshold Planner
Calculate an invoice-match threshold, build a reconciliation summary, and optionally deliver the resulting business record.
Audience Readiness Guide
Classify a stakeholder brief, create a client-facing preview from approved sections, and optionally deliver it while recording the outcome.
Service Class Planner
Service Class Planner converts a task profile into scheduling guidance and a task schedule, then saves the result locally or delivers it to a configured target.
Delivery Requirement Advisor
Determine whether a delivery requires a signature, create the corresponding documentation record, and optionally deliver it to a configured target.
Approval Group Directory
Identify the appropriate reviewer group, create a local business record, and optionally deliver the request to a configured external service.
Featured*
