List Fireflies Meetings: 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
Limit limit	number	Optional	Max meetings to return
Skip skip	number	Optional	Pagination offset

Sample request

{
  "limit": "{{trigger.limit}}",
  "skip": "{{trigger.skip}}"
}

Returns

{
  "data": {
    "transcripts": [
      {
        "id": "abc123",
        "date": 1712835600000,
        "title": "Weekly Sync",
        "duration": 1800,
        "host_email": "host@example.com"
      }
    ]
  }
}

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

FAQ

Questions about List Fireflies Meetings.

What does the List Fireflies Meetings action do in Fireflies?

Paginated meeting history with filters. Useful for "yesterday's calls digest" rollups or for backfill workflows on missed transcripts.

What inputs does List Fireflies Meetings require?

List Fireflies Meetings has no required inputs. Sensible defaults are applied if you leave fields blank.

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 List Fireflies Meetings support batch operations?

Yes. Run List Fireflies Meetings 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