Meetings & calls
An AI agent that turns Otter transcripts into follow-through.
Connect Otter and an OpenHelm agent can process new transcripts on a schedule, condense them into decisions and actions, and keep a running record of who owes what, delivered by email or into the tools you already use.
What agents do with Otter. Recurring jobs, checked every run.
Same-day meeting summaries
Condense each new transcript into a decisions-and-actions note and email it to the meeting owner before the end of the day.
Action-item register
Maintain a data table of actions across all meetings, with owner and due date, and chase items as they age.
Weekly themes review
Once a week, read across the transcripts for recurring topics and blockers and produce a short leadership brief.
Connect Otter. A few minutes, once.
Connect Otter
Add Otter under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Otter", "type": "token", "secret": "<your Otter API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
What happens to long transcripts?
Jobs run asynchronously in an isolated cloud environment with generous time budgets, so a two-hour transcript is processed the same way as a ten-minute one, and you get the finished summary when it completes.
How does OpenHelm connect to Otter?
With a scoped API key: create one in Otter, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Otter data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.