feat(n8n): wire notify and persist append logs

This commit is contained in:
zap
2026-03-12 15:03:35 +00:00
parent 9b8b744cb1
commit c1f851b451
6 changed files with 288 additions and 129 deletions

View File

@@ -95,16 +95,17 @@ This keeps the external surface small while letting n8n route internally.
### Import the shipped router workflow
Use the included workflow asset when you want a ready-made starter router for:
Use the included workflow asset when you want a ready-made local router for:
- `append_log`
- `notify`
- `append_log` → append small records into workflow static data (`actionLog`, latest 200)
- `notify` → send through the current Telegram + Discord notification paths
- normalized JSON success/failure responses
- unknown-action handling
Important:
- the workflow export intentionally leaves Webhook authentication unset
- after import, manually set **Authentication = Header Auth** on the Webhook node and bind a local credential using `x-openclaw-secret`
- the shipped asset already includes the live side-effect shape for local JSONL logging plus Telegram/Discord fan-out
See `references/openclaw-action.md` for import and test steps.
@@ -115,6 +116,7 @@ See `references/openclaw-action.md` for import and test steps.
3. If the shipped workflow should support it, update `assets/openclaw-action.workflow.json` and rerun `scripts/validate-workflow.py`.
4. Keep the first version small and explicit.
5. Only add the new endpoint to regular use after a successful `/webhook-test/` run.
6. For append-style event logging, prefer workflow static data for small recent breadcrumbs; use MinIO later for rotation, batching, archival, or sharing rather than tiny object-per-line writes.
## Environment variables