will/swarm-zap
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(n8n-webhook): add approval-gated notification executor

Browse Source
This commit is contained in:
zap
2026-03-12 17:41:59 +00:00
parent dc990a1af3
commit 1eabaeb652
7 changed files with 65 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
memory/2026-03-12.md
View File

@@ -69,3 +69,12 @@
- local HTTP URL `http://192.168.153.113:18808/healthz` → success
- `https://example.com` with `skip_ssl_certificate_validation: true` → success
- Cleanup: resolved the temporary verification approval items so `approvalQueue` ended empty after testing.
- State check before attempting deeper executor work: the live n8n instance currently exposes only four credentials via the public API — `Discord Bot Auth`, `Telegram Bot (OpenClaw)`, `OpenClaw Webhook Header`, and `Header Auth account`. No Gmail/Google Calendar credentials were present, so provider-backed email/calendar execution was intentionally not faked.
- Implemented the first true approval-gated executor that matches currently available creds:
- new action `send_notification_draft`
- queues a pending notification in `approvalQueue`
- when approved via `approval_queue_resolve`, it executes the existing `notify` path and sends through Telegram + Discord
- Verified live end-to-end on 2026-03-12:
- `send_notification_draft` returned `200` and produced pending id `approval-mmnr8pyq-tjxiqkps`
- approving that item via `approval_queue_resolve` returned `executed: true` and `executed_action: "notify"`
- `approval_queue_list` showed `pending_count: 0` afterward and recorded the execution metadata in history