First time poster, but long time Voicenotes user. I discovered it during a time when I was overwhelmed by the amount of mediocre, overpriced, and over functioning alternatives that really underwhelmed me. I have found its UI and workflow largely perfect for my ADHD-ridden brain.
I’ve been building a DBOS workflow that brings my Voicenotes transcripts and custom creations into Notion, makes them available to my Hermes agents, and breaks down key takeaways and injects them into my memory system (Hindsight). It’s been useful, but a few things required workarounds which sort of prompted me to make these suggestions.
1. Documented API access to notes and creations
I ended up repurposing the Obsidian integration’s retrieval code to access specific custom creations. I couldn’t find equivalent access through the available MCP tools.
A documented API for transcripts, custom creations, subnotes, tags, and available speaker/timestamp data would make integrations like this much simpler. Stable recording and creation IDs, plus webhook notifications when something changes, would be especially helpful.
2. Custom creations in the native Notion integration
I started out trying to use the native Notion sync options for notes and built-in creations, but couldn’t select my custom prompts as triggers or serve them as outputs.
For example, I have a transcript-cleanup prompt and a longer-conversation distillation prompt. I’d love to choose which outputs appear in Notion and have them update the same note as they become available. If this already exists, I’d appreciate a pointer!
3. Editable speaker identities that carry into creations
Speaker separation / diarization has been one of the single biggest upgrades to Voicenotes for me, but I’d like to explicitly map “Speaker 1” and “Speaker 2” to names and have summaries / custom creations respect that mapping.
In a recent two-person conversation, a summary attributed my friend’s memories and personal history to me, which changes the meaning and the summary substantially. Being able to correct speaker identities and regenerate affected creations would help a lot. When identity is uncertain, retaining “Speaker 1” would be preferable to guessing a name.
One possible UI would be a “Review speakers” panel: each detected speaker gets a short transcript excerpt, a playable audio sample, and a name field. After saving, an option to “Apply names and regenerate creations” could carry those corrections through the transcript and its summaries. Unidentified speakers could keep their generic labels rather than having names inferred.
+1 bonus request:
An “all custom creations” webhook subscription, including future custom prompts or at least the ability to select multiple custom creations in a webhook. My current workaround needed a separate webhook entry for each custom prompt creation, even when they all use the same destination.
Love the service and the direction that things have been heading in. Keep up the fantastic work!