Date: 2026-10-08 Channel: Megaphone Source: Michael Houck (U04V2LBL4RY), Blake Emal (U076187FXRQ) Permalink: https://ryevalley.slack.com/archives/C06UJ3V2HEV/p1791488533958069
Commitment
Michael said “Gonna work on it” in response to Blake Emal’s feedback that the newsletter workflow in Studio/Hermes is not optimized. Specifically, Michael proposed hooking Hermes up directly to each newsletter client’s beehiiv account via API (each workspace has its own API key that would need to be created). The goal: eliminate manual copy-paste from Hermes into beehiiv; Hermes would draft and potentially publish directly.
Blake Emal’s Feedback (Context)
Blake is going through the full Megaphone newsletter workflow end-to-end for the first time (with Adam Gillman as test case). His friction points:
- No starting-point templates from Hermes (newsletter name options, one-liner, welcome email)
- Research, sourcing, and hyperlinking are heavy lifts not suited to the current chatbot UX
- Imagery and template fitting add another manual layer
- Pasting into beehiiv is a separate painful step
Michael’s proposed solution: beehiiv API per client workspace. One API key per newsletter client, wired into Studio/Hermes. No pasting; Hermes drafts and potentially schedules directly in beehiiv.
Status
Commitment made; no timeline stated. Blocked on: (1) each beehiiv workspace needing its own API key created, (2) Michael building the functionality in Studio.
Watch
- Pally and Adam Gillman are the two active newsletter clients; both need this workflow
- Ben (ops) is managing beehiiv setup for Pally; Blake S for other clients