ToolsConnector
Fireflies
Search meeting transcripts, read a summary and analytics, or ask AskFred a question, from Claude or ChatGPT, through Tulina's own MCP server.
Official site: fireflies.ai
What it can do
4 read/1 write
- 01Read
Search transcripts by keyword, participant or date
- 02Read
Read a meeting's summary, sentences, analytics and participants in one call
- 03Write
Upload an audio file for transcription
- 04Read
Rename a meeting, make it private, or file it in a channel
- 05Read
Ask AskFred a question spanning your meetings
Fireflies configures its webhooks only from its own settings screen — there is no API for them at all — so this connector has none rather than pretending otherwise. Everything else is here, including the parts you would reach for in a workflow: one call returns a meeting's summary, its sentences and its analytics together, instead of three.
How do you connect Fireflies to Claude and ChatGPT?
Through Tulina's own MCP server, not Fireflies'. Search transcripts by keyword, participant or date, read a meeting's summary and analytics in one call, or ask AskFred a question spanning your meetings, in the same chat as the follow-up, whether that chat is Claude or ChatGPT.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Fireflies once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Fireflies at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Fireflies returns something usable instead of something generic.
Processes that run on Fireflies
None published yet.