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

feat(n8n): wire notify and persist append logs

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -22,3 +22,11 @@
- `notify` returned `200` with normalized JSON success payload
- unknown action returned `400` with `{ code: "unknown_action" }`
- The packaged skill artifact was refreshed after the router simplification at `/tmp/n8n-skill-dist/n8n-webhook.skill`.
- Follow-up implementation for real side effects:
- `notify` was successfully wired to the existing Telegram + Discord credentials and verified live multiple times.
- `append_log` hit two dead ends before settling on the clean solution:
1. `Execute Command` node was unavailable in this n8n build (`Unrecognized node type: n8n-nodes-base.executeCommand`).
2. `Read/Write Files from Disk` was available, but candidate paths were either missing or not writable in this container/runtime.
- Final fix: switched `append_log` to use n8n workflow static data (`$getWorkflowStaticData('global')`) under key `actionLog`, capped to the latest 200 entries.
- Verified persisted state via the n8n API: `staticData.global.actionLog` contains the live test record for request `live-log-003`.
- Conclusion: for small recent operational breadcrumbs, workflow static data is the right sink here; MinIO is better reserved for later archival/rotation/export use cases rather than tiny per-event appends.