Project · Saas Lifebot · Runbooks

Runbook — Health Auto Export ingest setup

Point Health Auto Export at the multi-user ingest endpoint for **one** user’s key.

type runbookstatus activelifebot · hae · ingest

Prerequisites

  • Vault created (so public key exists for seal-on-ingest)
  • Ingest key generated in Settings (copy once)
  • Public HTTPS or Tailscale URL reachable from phone

Steps

  1. Settings → generate ingest key → store in password manager.
  2. HAE → automation / REST: - URL: https://<host>/ingest/health (or Tailscale equivalent) - Header: x-lifebot-key: <user-ingest-key> - Method: POST JSON (HAE default body)
  3. Trigger a sync; confirm Settings/Health updates after unlock.
  4. Never share this key; rotating key invalidates old HAE config.

Verification

  • 200 from HAE
  • New sealed rows for that ownerId only
  • Other users unchanged

Rollback

Rotate ingest key in Settings; update or disable HAE automation.

Compiled from wiki/projects/SAAS-Lifebot/runbooks/hae-ingest-setup.md · git is the source of truth