Fireflies, without opening Fireflies.
Search every meeting the team has had, and send the bot into the next one.
- Free to start
- No card
- Nothing irreversible without your yes
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Fireflies details, and Ray takes it from there.
@Ray which meetings mentioned the migration deadline?
@Ray send Fireflies into the standup that just started.
@Ray who talked the most in the roadmap review?
@Ray clip the part where they described the bug.
What Ray can and cannot do in Fireflies
Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.
13 reads wired, 1 action Ray does at once, and 4 actions that wait for your yes.
Runs on its own
What Ray reads in Fireflies
- Transcripts by filter or by id, and a keyword search across titles and what was said
- Who attended, the topics the AI pulled out, and how long each person talked
- Highlight clips, AI app outputs, and team-level conversation analytics
- The team's users, their groups, and the channels meetings are filed into
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Rename a meeting
Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.
Asks first, every time
Always waits for your yes
- Send the Fireflies bot into a meeting that is already running
- Upload a recording for transcription, or clip a moment out of a transcript
- Move meetings into a channel
Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete a transcript
- Ask Fireflies' own assistant a question, because Ray reads the transcripts itself
- Grant or revoke admin, or change who can see a recorded meeting
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Fireflies actions that stop in the thread with the real content before they happen.
- Send Fireflies into a live meeting
- Upload audio to Fireflies for transcription
- Clip a moment out of a Fireflies transcript
- Move Fireflies meetings into a channel
Ray does these at once
- Rename a Fireflies meeting
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Send Fireflies into a live meeting
Showing Title, Meeting link, Attendees, Duration and Language, each carrying the exact content that will land.
How Ray works with Fireflies
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Fireflies
Fireflies has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
It lands, with an Undo
Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.
Megan
@Ray the checkout bug is back. Take a look in Fireflies, and tell Dana it is being looked at.
Rename a Fireflies meeting
- Done
- just now
Ray uses Fireflies together with the rest of your tools.
One ask can read Fireflies, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Fireflies to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Fireflies and it can do the Fireflies part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Fireflies has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Fireflies. Anything irreversible still waits for a yes.
Security and permissions
- You paste the Fireflies key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Fireflies in a message. Uninstall Ray and every connection it held is revoked.
Fireflies and Ray, answered
The questions teams ask before they connect Fireflies. Every answer is how this integration is built rather than a promise about it.
More calendars & scheduling integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Fireflies.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.