🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home n8n Workflow
January 22, 2026

Fireflies to Dart, meeting summaries that get reviewed

Lisa Granqvist Partner Workflow Automation Expert

Your meetings are recorded. The transcript exists. And somehow the “notes” still end up scattered across DMs, email threads, and half-finished docs that nobody reviews.

This Fireflies Dart integration hits project managers first, because you’re the one chasing decisions and next steps. But client-facing leads and ops managers feel the same drag when follow-ups go missing and context lives in five places.

You’re going to turn every processed Fireflies meeting into a clean Dart summary plus a built-in review task, so the right person actually checks it.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Fireflies to Dart, meeting summaries that get reviewed

Why This Matters: Meeting Notes That Don’t Get Used

Raw transcripts are useful, but they’re not operational. You still have to read them, pull out decisions, translate vague “we should” statements into action items, then paste the important parts somewhere your team will actually open. And if the notes live in a doc without a clear owner, they quietly die there. The cost isn’t just time; it’s the second meeting you have next week because nobody remembers what was agreed, plus the awkward “can you send the link again?” follow-up.

It adds up fast. Here’s where it breaks down in real teams.

  • Someone has to summarize each meeting manually, and that usually means about 20–30 minutes of focused work.
  • Links to the meeting recording and transcript get dropped into chat, then disappear under newer messages.
  • Action items aren’t assigned in the same place as the notes, so tasks become “floating intentions.”
  • Different people write notes differently, which means inconsistent quality and a lot more clarification later.

What You’ll Build: Fireflies Summaries That Land in Dart With a Review Task

This workflow kicks off when Fireflies.ai finishes processing a meeting and sends a webhook to n8n. n8n then pulls the full transcript from Fireflies, hands it to an AI agent (using a Gemini chat model in this workflow), and asks for a structured summary you can actually scan. That summary gets parsed into clean fields, then written into a Dart document inside the right workspace folder. Finally, the workflow finds your Dart task board and creates a review task that includes the meeting link, so someone is explicitly responsible for checking the notes and next steps.

In practice, you go from “a transcript exists somewhere” to “a summary is in the right place, formatted consistently, and queued for review.” Nothing fancy to babysit. Just a reliable handoff from meeting to documentation.

What You’re Building

Expected Results

Say your team runs 10 meetings a week that matter (sales calls, project check-ins, stakeholder updates). If someone spends about 25 minutes per meeting cleaning up notes and sharing links, that’s roughly 4 hours weekly. With this workflow, the “human time” becomes a quick skim during the Dart review task, maybe 5 minutes per meeting. You still wait for AI processing in the background, but you get about 3 hours back each week and your notes don’t disappear.

Before You Start

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Fireflies.ai for meeting transcripts and webhook events.
  • Dart to store summaries and create review tasks.
  • Fireflies API key (get it from your Fireflies settings/API area)

Skill level: Intermediate. You’ll paste a webhook URL, connect accounts, and edit a couple IDs (folder and board) without breaking the flow.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

Fireflies triggers the workflow via webhook. When a meeting finishes processing in Fireflies.ai, it sends a payload to your n8n webhook URL so the workflow can start without you touching anything.

n8n pulls the full transcript. Using the Fireflies transcript node, the workflow retrieves the transcript content (and typically the meeting metadata/link) so your summary isn’t based on partial notes.

AI generates a structured summary. The workflow passes the transcript into an AI agent connected to a Gemini chat model, which returns a consistent JSON-style summary (think: overview, decisions, action items, and any sections you choose to include).

Dart gets the doc and the review task. n8n finds the right workspace folder, creates a new Dart document containing the formatted summary, then locates your task board and creates a review task with the meeting link attached.

You can easily modify the summary sections to match your team’s meeting style, or route reviews to a different board based on meeting type. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Webhook Trigger

This workflow starts when an external system sends a POST request to a webhook URL.

  1. Add and open Incoming Webhook Trigger.
  2. Set HTTP Method to POST.
  3. Set Path to 437a1a60-35af-4c81-9058-176d825b7173.
  4. Use the generated webhook URL in the system that will send the meeting ID in the request body.

Tip: The webhook must receive a JSON body with meetingId because downstream nodes reference {{$json.body.meetingId}}.

Step 2: Connect Fireflies and Fetch the Transcript

This step pulls the meeting transcript using the ID from the webhook payload.

  1. Add and open Fetch Meeting Transcript.
  2. Set Transcript ID to {{$json.body.meetingId}}.
  3. Credential Required: Connect your firefliesApi credentials.
  4. Connect Incoming Webhook TriggerFetch Meeting Transcript.

⚠️ Common Pitfall: If the incoming request does not include meetingId, Fetch Meeting Transcript will fail because the expression {{$json.body.meetingId}} resolves to empty.

Step 3: Set Up AI Summarization

The transcript is summarized by an AI agent using Gemini as the language model, then parsed into JSON.

  1. Open Gemini Chat Engine and set Model Name to models/gemini-2.5-pro.
  2. Credential Required: Connect your googlePalmApi credentials in Gemini Chat Engine.
  3. Open Generate AI Summary and keep the Text prompt as provided (it enforces JSON-only output).
  4. Confirm Gemini Chat Engine is connected to Generate AI Summary as the language model (AI connection).
  5. Connect Fetch Meeting TranscriptGenerate AI SummaryParse Summary JSON.

Tip: Generate AI Summary references transcript fields like {{$json.data.summary.overview}} and {{$json.data.summary.action_items}}, so ensure the Fireflies response includes these keys.

Step 4: Configure Dart Document and Task Outputs

This section creates a summary document in Dart and then creates a review task linked to the document and Fireflies transcript.

  1. Open Locate Workspace Folder, set Resource to Folder and Operation to Get Folder, and set ID to [YOUR_ID].
  2. Open Generate Summary Document and set Resource to Doc and Operation to Create Doc.
  3. Set Item in Generate Summary Document to:
    ={"title":"{{ $('Fetch Meeting Transcript').item.json.data.title }}","text":"Overview:\n\n{{ $('Parse Summary JSON').item.json.summary.overview }}\n\nSummary:\n\n{{ $('Parse Summary JSON').item.json.summary.summary }}\n\nKey items:\n\n{{ $('Parse Summary JSON').item.json.summary.key_items }}\n\nAction Items:\n\n{{ $('Parse Summary JSON').item.json.summary.action_items }}"}
  4. Open Locate Task Board, set Resource to Dartboard, Operation to Get Dartboard, and ID to [YOUR_ID].
  5. Open Fetch Created Document, set Resource to Doc, Operation to Get Doc, and set ID to {{$('Generate Summary Document').item.json.item.id}}.
  6. Open Create Review Task and set Resource to Task and Operation to Create Task.
  7. Set Item in Create Review Task to:
    ={"title":"Review recent meeting: {{ $('Fetch Meeting Transcript').item.json.data.title }}","description":"View meeting summary here: {{ $json.item.htmlUrl }} \n \n [Fireflies meeting link]({{ $('Fetch Meeting Transcript').item.json.data.transcript_url }})"}
  8. Credential Required: Connect your dartApi credentials to all Dart nodes (5 nodes handle folders, documents, and tasks).

⚠️ Common Pitfall: Replace [YOUR_ID] in Locate Workspace Folder and Locate Task Board with real Dart folder/board IDs, or the document and task will not link correctly.

Step 5: Verify Execution Flow and Non-Operational Nodes

Confirm the linear flow and note that the sticky note is informational only.

  1. Ensure the chain follows: Incoming Webhook TriggerFetch Meeting TranscriptGenerate AI SummaryParse Summary JSONLocate Workspace FolderGenerate Summary DocumentLocate Task BoardFetch Created DocumentCreate Review Task.
  2. Keep Flowpast Branding in place as a reference node; it does not affect execution.

Tip: The workflow has no parallel branches, so failures are easier to trace sequentially.

Step 6: Test and Activate Your Workflow

Run a full test to confirm the webhook, summary generation, and Dart outputs work as expected.

  1. Click Execute Workflow and send a POST request to the Incoming Webhook Trigger URL with a JSON body like {"meetingId":"YOUR_TRANSCRIPT_ID"}.
  2. Verify Fetch Meeting Transcript returns transcript data and Generate AI Summary outputs JSON in the output field.
  3. Confirm Parse Summary JSON produces structured fields under summary.
  4. Check that Generate Summary Document creates a Dart doc and Create Review Task creates a task with the document and Fireflies link.
  5. When satisfied, toggle the workflow to Active for production use.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

  • Dart credentials can expire or lack folder permissions. If document creation fails, check your Dart workspace and folder access settings first.
  • Fireflies webhooks are picky about environments. Make sure you copied the PROD webhook URL from n8n into Fireflies, not a test URL that changes.
  • AI output can drift if the prompt is vague. Tighten the prompt and require valid JSON early, or your “Parse Summary JSON” code step will fail on messy formatting.

Quick Answers

What’s the setup time for this Fireflies Dart integration automation?

About 30 minutes if you already have Fireflies and Dart set up.

Is coding required for this meeting summary automation?

No. You will connect accounts and update a few IDs and settings in n8n.

Is n8n free to use for this Fireflies Dart integration workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in AI model costs (Gemini usage varies by plan) and any Fireflies.ai API access tied to your account.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this Fireflies Dart integration workflow for different use cases?

Yes, and you should. The easiest win is editing the prompt used by the “Generate AI Summary” agent so it matches your format (sales calls vs. sprint planning notes feel totally different). You can also adjust the “Parse Summary JSON” code step to add or rename fields, then map those into the Dart document template. Common tweaks include adding a “Risks” section, tagging the meeting type, and routing review tasks to different Dart boards based on who hosted the call.

Why is my Dart connection failing in this workflow?

Usually it’s permissions. Reconnect Dart in n8n, then confirm the integration has access to the workspace and the specific folder where you’re trying to create documents. After that, double-check the Folder ID and Dartboard (task board) ID in the relevant Dart nodes, because dummy IDs will “work” up to the point where Dart rejects the write.

What volume can this Fireflies Dart integration workflow process?

On most small-team setups, processing dozens of meetings a day is fine, because each meeting is a single run plus an AI call. n8n Cloud limits depend on your plan’s monthly executions, while self-hosting has no fixed execution cap and is mostly constrained by your server. If you start pushing hundreds of meetings weekly, watch AI rate limits and keep an eye on Fireflies webhook delivery so you don’t queue too much at once.

Is this Fireflies Dart integration automation better than using Zapier or Make?

Often, yes. n8n is much better when you need “real” logic like structured JSON parsing, branching, and multi-step document + task creation in one scenario. It’s also flexible about hosting, which matters if you want more runs without paying per task. Zapier and Make can still work for basic “meeting finished → send recap” flows, but this one benefits from the control you get in n8n. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation.

Once this is running, meeting documentation stops being a recurring chore and turns into a repeatable system. The workflow handles the busywork so your team can focus on the work that actually moves.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Launch login modal Launch register modal