Zapier integration: a "note ready" trigger surface (webhook-first) #414

Second half of ruzin's integrations push (Obsidian tracked separately). Zapier is the bigger lift because Steno currently has no event surface an external automation can subscribe to.

Proposed staging

Stage 1 - outgoing webhook (no Zapier account needed, generic): a setting (off by default) to POST a JSON payload to a user-configured URL when a note finishes processing ("note ready"): title, date, folder, summary markdown, optionally the transcript (separate toggle - privacy). With Zapier's "Webhooks by Zapier" trigger this already enables Slack/Notion/CRM/etc. flows without us building anything Zapier-specific. Also works with n8n/Make/self-hosted automation - fits the privacy-conscious user base better than a hosted-only path.

• Privacy defaults: off by default, explicit opt-in, clear disclosure that the payload leaves the machine, transcript excluded unless separately enabled.
• Delivery: fire-and-forget with one retry; failures logged, never blocking the pipeline.

Stage 2 (optional, later) - a listed Zapier app: requires a hosted trigger API + auth story, i.e. real server-side infrastructure Steno deliberately doesn't have today. Only worth evaluating if Stage 1 sees real usage. Possibly ties into the org adapter rather than the desktop app.

Open questions

• Payload schema: worth versioning from day one (schema_version) so integrations don't break.
• Should "recording started/stopped" events be included, or notes only? (Notes-only keeps the privacy story simplest.)
• HMAC signature header for receivers that want authenticity?

Non-goals (this issue)

A hosted Zapier app, incoming webhooks/remote control, per-event filtering UI.