Omi
Bring Omi wearable conversations into Helix. Work conversations collect in your Meeting Capture tray and go to Dead Drop in batches as tickets, time, tasks and follow-ups.
Required Credentials
1 fieldEach person pastes their own Omi developer key in My Profile → Meeting Capture (app.omi.me/developers → key with conversations:read).
Data Flow
4 capabilitiesWork conversations batched into Dead Drop
Promises, requests, approvals, time and follow-ups from real conversations become Dead Drop proposals. Personal conversations are never stored.
Find a conversation
Find what was said or decided in any recorded conversation and bring it straight into Dead Drop.
Recording consent tracking
Helix finds the consent question in the recording, records who agreed, and warns wherever a conversation without consent is used.
Voice commands
Commands are queued for the Command Bar so it can ask its questions later. "Do it now" runs immediately only when there are no questions, it is low risk, and nothing goes to a client, touches money, or deletes anything, with Undo.
What Helix does with Omi recordings
Every recording system on this shelf feeds the same Helix Meeting Capture engine. Wear it, record the call, or let the bot join the meeting — these 72 moments are what happen next.
Ready to connect?
Log into Helix and open App Marketplace to configure this integration.