Short answer: Drop the "Fireflies → Get Fireflies Transcript" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Transcript ID transcript_id | string | Required | The Fireflies transcript ID. Use Search Transcripts or List Meetings to find it. |
{"transcript_id": "{{trigger.transcript_id}}"}
{"data": {"transcript": {"id": "abc123","date": 1712835600000,"title": "Weekly Sync","summary": {"overview": "Discussed Q3 roadmap and hiring plan.","action_items": ["Send follow-up to design team"]},"duration": 1800,"host_email": "host@example.com","meeting_link": "https://meet.example.com/xyz","participants": ["host@example.com","guest@example.com"],"transcript_url": "https://app.fireflies.ai/view/abc123"}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.