ACTION_ID: get_fireflies_meeting_transcription
NAME: Fireflies: Meeting Transcription Lookup
CATEGORY: research
CREDITS: 0

Transcript of your meetings.

Typically triggered by a Fireflies webhook fired after a meeting finishes
recording and transcribing.

================================================================================
PREREQUISITE — USER ACTION REQUIRED
================================================================================

This action only works if the user has connected their Fireflies account
in Floqer. The connection cannot be made via the API or by an AI agent.

The user must do this themselves before this action will run:
  1. Sign in to Floqer at https://app.floqer.com
  2. Open the Connections page from the sidebar
  3. Click Fireflies and complete the OAuth flow

If the user has not connected Fireflies, this action will fail with a
connection / authentication error. Before configuring or running this
action, confirm with the user that the Fireflies connection exists.

INDEX:
  1. Inputs
  2. Outputs
  3. How to configure
  4. Where it fits in a workflow
  5. When to use

================================================================================
1. INPUTS
================================================================================

transcribe_id (string, required)
  Transcribe ID. Unique ID of the transcribe you want to fetch.

================================================================================
2. OUTPUTS
================================================================================

meeting_notes (string) — Meeting Notes. Placeholder: "A timeline of the
  transcribed meeting".
meeting_participants (string) — Meeting Participants. Placeholder:
  "Display name, email, phone number of the meeting participants".

================================================================================
3. HOW TO CONFIGURE
================================================================================

Configure Action body:

{
  "inputs": {
    "transcribe_id": "{{input.transcribe_id}}"
  }
}

Pass the Fireflies transcribe ID as `transcribe_id` — typically the
`{{input.transcribe_id}}` value populated by the inbound Fireflies
webhook (see WHERE IT FITS).

================================================================================
4. WHERE IT FITS IN A WORKFLOW
================================================================================

UPSTREAM — how transcribe_id reaches the workflow
  Fireflies records and transcribes the meeting, then fires a webhook to
  the Floqer workflow's webhook URL. The webhook payload includes the
  meeting's transcribe_id. The workflow's input field "transcribe_id" is
  populated from the webhook body. This action then reads that input via
  {{input.transcribe_id}}.

  The user sets the webhook up once in Fireflies, pointing it at the
  Floqer workflow's webhook URL. From then on every recorded meeting
  auto-fires a workflow run.

THIS ACTION
  Fetches the full transcript and attendee list for the given
  transcribe_id from Fireflies.

DOWNSTREAM — typical chains after this action
  Insight extraction:  this -> llm_models (summarize, extract action
                       items, surface objections / next steps).
  Slack notification:  this -> llm_models -> slack_send_message (post a
                       summary of the call insights to a Slack channel
                       so the rep / team gets a notification).
  CRM update:          this -> llm_models -> hubspot_update_object /
                       salesforce_update_record (push the extracted
                       insights onto the contact or opportunity).
  Email drafting:      this -> llm_models (draft a follow-up email
                       referencing what was discussed).

================================================================================
5. WHEN TO USE
================================================================================

- Push call insights into the CRM (e.g. update HubSpot/Salesforce contact
  or opportunity with key discussion points, action items, and next-step
  owner).
- Send a Slack notification with a summary of the call insights so the
  rep or team is alerted right after the meeting.
- Prepare next-step notes or task lists for the rep before their next
  touchpoint.
- Draft a follow-up email referencing what was discussed in the call.

================================================================================

This file is maintained manually. Last updated: 2026-04-28.
Full interactive reference: https://floqer.com/docs/reference
Action catalog: https://floqer.com/docs/action-catalog.txt