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

fix(n8n-webhook): auto-load local gog automation env

Browse Source
This commit is contained in:
zap
2026-03-12 19:16:24 +00:00
parent afa48a3aa6
commit 044e36f385
4 changed files with 39 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -94,3 +94,8 @@
- email draft item id `approval-mmnsx7iz-k26qb60c` → `execution.op = gmail.drafts.create`, `status = dry_run`
- calendar item id `approval-mmnsx7ji-3rt7yd74` → `execution.op = calendar.create`, `status = dry_run`
- Current practical next step for real Gmail/Calendar execution: provide `GOG_KEYRING_PASSWORD` to the runtime environment that will invoke the bridge script, or switch `gog` to a keyring backend that supports unattended access on this host.
- Follow-up completion on 2026-03-12:
- stored local-only Gog automation env in `/home/openclaw/.openclaw/credentials/gog.env` with restrictive permissions (`600`)
- updated `resolve-approval-with-gog.py` to auto-load that file when present
- verified non-interactive headless Gmail access works using the stored env (successful `gog gmail search ... --json --no-input`)
- verified the bridge itself auto-loads the env file by resolving a fresh `email_draft` approval item in `--dry-run` mode and attaching execution metadata successfully without manually exporting `GOG_ACCOUNT` / `GOG_KEYRING_PASSWORD`