Fireflies
Fireflies meeting transcripts and summaries
Fireflies records, transcribes, and summarises meetings (Zoom, Google Meet, Microsoft Teams, in-person via the Fireflies app). Tiny Command surfaces two terminal triggers: Meeting Completed (the call ended; the recording is uploading) and Transcript Ready (the transcript has finished processing and is available for download — typically 5-15 minutes after the meeting ends for a 30-minute call). Four actions cover the reads: Get Meeting (metadata, attendees, duration, recording URL), Get Transcript (the full transcript with speaker labels, timestamps, and confidence scores), List Meetings, and Search Transcripts (full-text search across the user's transcript corpus — useful for "find every call where competitor X was mentioned"). The connection uses a Fireflies API key from the user's integrations page. Transcript Ready is the high-value workflow trigger because Meeting Completed fires too early for any analysis workflow that needs the actual text. The transcript payload includes speaker-attributed sentences plus Fireflies's auto-generated AI summary (overview, action items, key questions) when the workspace has AI summaries enabled.
Workflows start when Fireflies does.
2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a Fireflies-captured meeting ends. The recording is uploading but transcript isn't ready yet. For workflows that just need to know the meeting happened without the transcript.
Fires when the transcript has finished processing (typically 5-15 minutes after meeting end). The high-value trigger for analysis workflows — summarise, extract action items, sync to CRM with the meeting context.
Do anything Fireflies can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Fireflies Meeting | Returns meeting metadata — duration, attendees, recording URL, transcript availability flag. The standard lookup for workflows triggered on meeting completion. |
| Get Fireflies Transcript | Returns the full transcript with speaker labels, timestamps, plus Fireflies's auto-generated AI summary (overview, action items, key questions). For post-call analysis workflows. |
| List Fireflies Meetings | Paginated meeting history with filters. Useful for "yesterday's calls digest" rollups or for backfill workflows on missed transcripts. |
| Search Transcripts | Full-text search across the user's transcripts. Useful for "find every call where the customer mentioned competitor X" or "show me all calls discussing pricing" analytical workflows. |
Pre-built Fireflies workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Fireflies once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Fireflies field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Fireflies integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Fireflies to Tiny Command?
What Fireflies triggers does Tiny Command support?
What Fireflies actions can I run from a workflow?
Is the Fireflies integration real-time?
Do I need to write code to use Fireflies with Tiny Command?
How much does the Fireflies integration cost?
More calendar & scheduling apps people connect.
Same category as Fireflies, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Fireflies.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
