Skip to main content

​
What It Does

  • Automatically captures new meeting transcripts as soon as meetings end.
  • Logs detailed transcripts for pipeline reviews and coaching loops.
  • Ensures post-meeting data flows seamlessly into your dashboards or CRM.
  • Saves manual upload time and maintains consistent meeting records.

​
🏁 Getting Started

Fireflies Node config screenshot
1

Select Account

Choose your Fireflies account where meeting data is stored.
2

Configure Inputs

Connect your database and set how often to check for new transcripts.

​
Inputs

​
🛠️ Required Fields

  • Select Fireflies Account (✅)
    Connects your Fireflies workspace to read new meetings.
    Why it matters: Ensures the node has access to fresh meeting transcripts for your workflows.
  • Database Connection (✅)
    Choose where to store or reference previous meeting records.
    Why it matters: Helps dedupe and archive transcripts so only new meetings trigger workflows.
  • Polling Interval (✅)
    Defines how often (in seconds) to check for new meetings (default: 900).
    Why it matters: Balances timely data sync with system load—set shorter intervals for near-real-time alerts.

​
🎯 Optional Fields

None

​
Output

This trigger emits a structured event whenever Fireflies creates a new meeting with transcript data, including:
  • Meeting ID, title, participants, start/end times.
  • Full transcript text and summary metadata.
  • Attachments like recording URLs or audio snippets.
Use this output to feed downstream nodes for CRM updates, AI summaries, or notifications.
Fireflies Node output screenshot
Transcripts longer than supported lengths may be split and tagged sequentially.

​
How It Works

  1. Polls your Fireflies account at the defined interval.
  2. Checks each meeting for new transcripts against your database.
  3. Emits a new event when it detects an unprocessed meeting transcript.
  4. Triggers downstream actions like CRM logging, summary generation, or team alerts.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
CRM Meeting Logger”When a meeting ends, log the full transcript to Salesforce under the Deal ID.”
Team Knowledge Base Sync”Add new meeting transcripts to our Notion database for Sales training.”
Post-Meeting Summary Alerts”Generate and email a summary whenever a sales strategy meeting finishes.”

​
✨ Pro Tips

  • Confirm your Fireflies connection and permissions before saving the node.
  • Use @Transcript or Insert Input to pass specific fields downstream.
  • Adjust the polling interval to prevent hitting rate limits.

​
⚠️ Important Considerations

  • Very long transcripts can extend processing time—consider shorter meeting lengths.
  • Ensure your database connection is stable and has write permissions.
  • Polling too frequently may count against API limits.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
No meetings detectedIncorrect Fireflies account or permissionsRe-authenticate your Fireflies account.
Duplicate events firingDatabase check skipped or resetVerify your DB dedupe logic and reconnect node.
Missing transcript textRecording processing delayWait a few minutes or adjust the polling interval.

​
📝 FAQ

Yes — adjust Polling Interval to a higher value for fewer checks.
Use your database query to filter by meeting title or participants.
This is a trigger node since it starts your workflow on new meeting transcripts.

​
💰 Pricing

ActionCredit Cost
Trigger Run (per event)1 credit
Trigger nodes that start workflows (like “New Meeting Created”) cost 1 credit per event.
Action nodes like enrichment or formatting are free.

Drop this Fireflies node into your flow to automate transcript ingestion and keep your teams aligned—instantly. 🚀