docs(infra): record local n8n agent service

This commit is contained in:
zap
2026-03-12 06:34:08 +00:00
parent 680daf9964
commit a6434e5a02
2 changed files with 25 additions and 0 deletions

View File

@@ -115,6 +115,21 @@ Skills are shared. Your setup is yours. Keeping them apart means you can update
- Native Brave Search API (`web_search`) configured on 2026-03-10.
- Plan/rate note: Brave free plan hit `rate_limit: 1`; serialize requests instead of parallel bursts.
- **n8n-agent**
- Image: `docker.n8n.io/n8nio/n8n:latest`
- Container: `n8n-agent`
- Port: `18808 -> 5678`
- Health: healthy when last verified by host runtime output on 2026-03-11
- URL(s):
- `http://192.168.153.113:18808`
- `http://192.168.153.117:18808`
- `http://100.123.88.127:18808`
- Role: dedicated local n8n instance for agent-oriented workflows on the LAN
- Notes:
- initial host-port attempt on `18806` conflicted with another host listener; service was moved to `18808`
- webhook path `openclaw-ping` was created and tested end-to-end
- prefer narrow webhook-based integration before giving broad n8n admin/API control
### Embeddings (local)
- Runtime: Ollama

10
memory/2026-03-12.md Normal file
View File

@@ -0,0 +1,10 @@
# 2026-03-12
## n8n local documentation fix
- Documented the local `n8n-agent` service in `TOOLS.md` after noticing it had been set up but not captured in workspace notes.
- Recorded current known service details from prior host/runtime evidence:
- port `18808 -> 5678`
- LAN/Tailscale URLs
- dedicated agent-oriented n8n instance
- `openclaw-ping` webhook path tested end-to-end
- Operating note: prefer narrow webhook-first integration rather than broad n8n admin/API access.