File Fireflies user research interviews in Notion with a Slack TL;DR

After every user research interview in Fireflies, file a structured insight page in your Notion research database and post a three-bullet TL;DR to your team's Slack channel.

Agentic Task
Fireflies.aiNotionSlackProductOperationsMeeting WorkflowsFeedback TriageResearch & Monitoring

Build an agent workflow that fires every time Fireflies.ai finishes processing a meeting. The trigger is a webhook from Fireflies.ai on the meeting processed event.

When the webhook fires, do this:

1. Call Fireflies.ai Get Transcript with the meeting ID from the webhook payload to pull the full transcript, summary, attendees, and organizer.

2. Skip the run unless the meeting looks like a user research interview. Match if the title contains any of: 'interview', 'user research', 'discovery'. Also allow the meeting through if the organizer email is in a configured list of researcher organizers. If neither matches, stop quietly without writing anything downstream.

3. Have the agent synthesize the transcript into the fields the Notion research database expects: interviewee name and role, customer segment, jobs to be done, top observed pains (what they are struggling with today), feature requests (what they explicitly asked for), verbatim quotes worth saving (do not paraphrase, keep the wording exactly as said), and theme tags. Keep observed pains and requested solutions clearly separate so the database stays useful for theme rollups later.

4. Call Notion Create a Page as a child of the research database. Map the synthesized fields onto the database properties (do not dump everything into the page body). Paste the full transcript into the page body so the page stays searchable later. Keep fields tight and quotes verbatim.

5. Call Slack Send a Message to the research channel with a tight three-bullet TL;DR: one bullet for the biggest observed pain, one for the top feature request, one for the standout verbatim quote. Include the link to the new Notion page so the team can click through for the full insight.

I will provide: the Notion research database ID, the Slack channel, the title patterns that count as a research interview, and the optional list of researcher organizer emails.

Additional information

What does this prompt do?
  • Triggers the moment Fireflies finishes processing a user research interview, so insight reaches the team while it is still fresh.
  • Reads the full transcript, keeps observed pains separate from feature requests, and pulls out verbatim quotes worth saving.
  • Creates a structured page in your Notion research database with interviewee, segment, jobs to be done, pains, requests, quotes, and theme tags, and pastes the transcript into the page body so anyone can search it later.
  • Posts a three-bullet TL;DR plus a link to the Notion page in your research Slack channel.
What do I need to use this?
  • A Fireflies.ai account that records your user research interviews.
  • A Notion workspace with a research insights database shared with the General Input connection.
  • A Slack workspace and the channel where your team watches for new customer signal.
How can I customize it?
  • Decide which meetings count as research interviews by title pattern (interview, user research, discovery) or by listing your researcher organizers.
  • Map the agent's output to the exact fields in your Notion research database, including segment, jobs to be done, pains, requests, quotes, and theme tags.
  • Change the Slack channel, tweak the three-bullet TL;DR format, or adjust how the link to the Notion page is presented.

Frequently asked questions

Does this run on every Fireflies meeting?
No. It skips anything that does not look like a user research interview, based on a title pattern (interview, user research, discovery) or a list of researcher organizers you configure. Sales calls and internal meetings are filtered out.
What ends up in the Notion page?
The page properties hold structured fields like interviewee name and role, segment, jobs to be done, top pains, feature requests, quote highlights, and theme tags. The full transcript is pasted into the page body so the page stays searchable later.
Will it mix up customer pains with feature requests?
No. The agent is told to keep observed pains and requested solutions clearly separate so the database stays useful for theme rollups. Quotes are kept verbatim, not paraphrased.
Can I send the TL;DR somewhere other than Slack?
Yes. You can swap the Slack step for email, Microsoft Teams, or any other channel where your team already watches for fresh customer signal.
Do I need a paid Fireflies plan?
You need a Fireflies plan that allows pulling transcripts through their API. Most paid Fireflies tiers cover this. The free tier has tight daily limits, so a paid plan is recommended for steady use.

Stop letting research insights die in meeting recordings.

Connect Fireflies, Notion, and Slack once, and Geni files every user research interview the moment it finishes processing.