Connect Fireflies to Crush
Give Crush governed access to Fireflies’s 8 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Fireflies to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Fireflies in Runlayer
Add Fireflies from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Fireflies’s 8 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Fireflies
Sign in the way Fireflies requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Fireflies from Crush
Fireflies’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
8 Fireflies tools in Crush
Runlayer policy decides which of these Crush users can call. 8 read data only.
Get meeting details
Fetches detailed meeting transcript by ID, with optional field filtering.
Get meeting summary
Fetches meeting summary by ID, with optional field filtering.
Search meetings
Queries multiple meeting transcripts using filter properties (date, keyword, email, etc.).
Get user details
Fetches user account details.
Get user groups
Fetches user groups for the authenticated user or their team.
Get user contacts
Fetches contact list for the authenticated user.
Search meeting transcripts
Advanced search for meeting transcripts using a mini grammar.
Fetch meeting details
Retrieve complete meeting transcript with full conversation, metadata, and insights for a specific meeting ID.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Fireflies call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more
