Meetings & calls
An AI agent that acts on your Fireflies transcripts.
Connect Fireflies and an OpenHelm agent can read new meeting transcripts on a schedule, pull out decisions and action items, file summaries where your team works, and track commitments in a data table so nothing agreed in a call quietly disappears.
What agents do with Fireflies. Recurring jobs, checked every run.
Post-meeting action extraction
After each recorded meeting, extract owners, actions and deadlines into a data table and email the list to attendees the same day.
Weekly meetings digest
Summarise the week of calls into themes, decisions and open questions, one email instead of ten transcripts.
CRM note filing
For customer calls, write a concise summary and next steps to the matching record in your connected CRM.
Commitment follow-through
Track promises made in calls, such as sending a proposal by Friday, and nudge the owner before the deadline passes.
Connect Fireflies. A few minutes, once.
Connect Fireflies
Add Fireflies 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": "Fireflies", "type": "token", "secret": "<your Fireflies API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
Does the agent join my meetings?
No. Fireflies records and transcribes as it already does; the OpenHelm agent works with the transcripts afterwards, on the schedule you set.
How does OpenHelm connect to Fireflies?
With a scoped API key: create one in Fireflies, 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 Fireflies 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.