An n8n workflow blueprint that orchestrates two systems I built and self-host: a morning brief assembled from my own infrastructure, with no credentials stored in the workflow.
Most workflow demos call two public SaaS APIs and a weather service. This one calls my own production services: Mneme, a self-built semantic memory hub (65 MCP tools, 30 REST endpoints, PostgreSQL/pgvector, 593 tests) that every agent in my homelab shares, and Aegis, my secrets broker and SSH certificate authority, which mints scoped, short-TTL, audited credentials at runtime.
The design point is the credential path: the workflow stores no service API keys. Its only credential is a single scoped broker key. Every run asks Aegis for a token, uses it once against Mneme, and lets it expire. Canary secrets in the broker tripwire-alert if anything reads what it shouldn't.
Lane 1 — the morning brief
GET aegis.androux.org/v1/secret/mneme/api-tokenAuthorization: Bearer {{token}}Priority: high. The phone buzzes like it means it.Lane 2 — brain-dump intake
No service API keys are stored in this workflow; its only credential is one scoped broker key. Aegis mints everything else at runtime, short-TTL and audited, and canary secrets tripwire-alert if anything reads what it shouldn't. The intake webhook is header-auth gated, and the ntfy topic stays an env placeholder: public ntfy.sh topics are world-writable.
Same network philosophy as the rest of the homelab: LAN-only services, TLS via reverse proxy, nothing exposed to the internet. Which is also why this page is a blueprint rather than a public live demo. Root cause of most morning incidents remains: DNS. (It's always DNS.)