Skip to main content
Human guide: work with your agent → Inspect one Fireflies.ai action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Start with fireflies_transcripts to discover meeting IDs. Use limit and skip to paginate. Fireflies allows at most 50 transcripts per request. Use keyword, date bounds, organizers, participants, channel, host, or mine to narrow the list. Use fireflies_transcript when you need the full meeting record. It includes sentences, summaries, analytics, attendee data, transcript_url, audio_url, and video_url. Fireflies exposes recordings through transcript media URLs rather than a separate videos endpoint. Use IDs returned by list actions for channel, bite, AskFred, live-meeting, sharing, and update actions. Treat delete, upload, share, role, AskFred, and meeting-update actions as writes: confirm user intent and exact IDs before execution. fireflies_rule_executions_by_meeting and fireflies_audit_events may require an enterprise Fireflies plan. All actions require a customer-owned Fireflies API key. Deepline does not bill for Fireflies usage.

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.