Get Fireflies Meeting: Fireflies action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Meeting ID meeting_id	string	Required	The Fireflies meeting/transcript ID

Sample request

{
  "meeting_id": "{{trigger.meeting_id}}"
}

Returns

{
  "data": {
    "transcript": {
      "id": "abc123",
      "date": 1712835600000,
      "title": "Weekly Sync",
      "summary": {
        "overview": "Discussed Q3 roadmap.",
        "action_items": []
      },
      "duration": 1800,
      "host_email": "host@example.com",
      "transcript_url": "https://app.fireflies.ai/view/abc123"
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Fireflies Meeting.

What does the Get Fireflies Meeting action do in Fireflies?

Returns meeting metadata — duration, attendees, recording URL, transcript availability flag. The standard lookup for workflows triggered on meeting completion.

What inputs does Get Fireflies Meeting require?

Required: Meeting ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Fireflies returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Fireflies Meeting support batch operations?

Yes. Run Get Fireflies Meeting inside a Loop node to process arrays. Tiny Command handles Fireflies's rate limits automatically so you don't have to throttle manually.

More actions