Skip to main content

​
What It Does

  • Automatically uploads meeting recordings to Fireflies for transcription.
  • Provides searchable transcripts for deal reviews, onboarding, or training.
  • Shares completed transcripts with your team via webhook or rerun callbacks.
  • Centralizes meeting data, making follow-ups and summaries effortless.

​
🏁 Getting Started

Fireflies Upload Audio Node config screenshot
1

Select Account

Choose your connected Fireflies account to send audio files.
2

Configure Inputs

Provide the audio URL, meeting title, and optional webhook or rerun callback.

​
Inputs

​
🛠️ Required Fields

  • Fireflies Connection (✅)
    Select the Fireflies workspace where uploads will be stored.
    Why it matters: Ensures transcripts land in the right account and workspace.
  • URL (✅)
    The publicly accessible HTTPS link to your audio or video file (mp3, mp4, wav, m4a, ogg).
    Why it matters: Allows Fireflies to download and transcribe your recording without access errors.
  • Title (✅)
    The name for this meeting or recording.
    Why it matters: Labels your transcript, making search and organization easy.

​
🎯 Optional Fields

  • Webhook URL (⚪️)
    Where to send a POST request when transcription is complete.
    Why it matters: Automate follow-up workflows, like sending transcripts to Slack or your CRM.
  • Callback With Rerun (⚪️)
    Use Pipedream’s rerun helper to automatically retry this step upon transcription completion.
    Why it matters: Keeps your workflow in sync without manual triggers, but will increase execution time and credits.

​
Output

Upon successful upload, this node returns meeting metadata, including:
  • Transcript ID
  • Meeting status
  • Download URL for transcript (when ready)
  • Raw response object for downstream steps
Use these outputs to feed into CRM updates, notifications, or analytics workflows.
Fireflies Upload Audio Node output screenshot
You can map the Transcript ID and Download URL into your CRM or notification steps for seamless integration.

​
How It Works

  1. Sends your audio URL and title to Fireflies via a GraphQL upload mutation.
  2. Fireflies downloads and processes the file in supported formats.
  3. The meeting is stored and queued for transcription.
  4. On completion, triggers your webhook or rerun callback with transcript details.

​
🚀 Example Use Cases & Prompts

Use CaseSetup or Prompt Example
Sales Call Transcript”Upload my sales call recording URL for instant transcript in my CRM.”
Deal Handoff Documentation”Send demo recording to Fireflies and post transcript to deal channel.”
Weekly Standup Archive”Transcribe our team standup and share the summary link with Slack.”

​
✨ Pro Tips

  • Double-check your audio URL is a direct download link, not a preview.
  • Use @TranscriptID in downstream steps to fetch or route transcripts automatically.
  • Keep titles consistent (e.g., Deal Name - Meeting Date) for easy filtering.

​
⚠️ Important Considerations

  • Large files may take longer to process—plan accordingly.
  • Ensure your webhook endpoint can handle POST requests with JSON payloads.
  • Callback reruns consume extra credits and execution time.

​
🛠 Troubleshooting & Gotchas

SymptomLikely CauseQuick Fix
Upload failsInaccessible or invalid URLVerify HTTPS link is public and downloadable.
Missing transcript updatesWebhook endpoint misconfiguredCheck endpoint URL and listen for POST requests.
Excess credit usageFrequent reruns with large filesDisable callback rerun or limit file size.

​
📝 FAQ

Not directly—you’ll need to loop this action for each URL in your workflow.
Fireflies supports mp3, mp4, wav, m4a, and ogg files.
You’ll receive an error in the response; implement error handling or retry logic in your workflow.

​
💰 Pricing

ActionCredit Cost
Upload AudioFree
Action nodes like this are free, so you can transcribe as many meetings as you need without extra credits.

Drop this Upload Audio node into your flow to centralize meeting transcripts and accelerate your GTM workflows — automatically. 🚀