Short answer: Drop the "Fireflies → Search Transcripts" 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 |
|---|---|---|---|
Title Contains title | string | Optional | Match against meeting title |
Participant Email participant_email | string | Optional | Filter to meetings where this email attended |
From Date from_date | string | Optional | ISO 8601 date (inclusive) |
Limit limit | number | Optional | Max results to return |
{"title": "{{trigger.title}}","participant_email": "{{trigger.participant_email}}","from_date": "2026-01-01","limit": "{{trigger.limit}}"}
{"data": {"transcripts": [{"id": "abc123","date": 1712835600000,"title": "Weekly Sync","duration": 1800,"host_email": "host@example.com","participants": ["host@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.