Connecting Meeting Notes to Your PM Tools with Fireflies.ai Integrations

Check your current Fireflies plan at fireflies.ai/account. PM tool integrations (Asana, Jira push) require Business plan. Slack and email integrations are available on Pro.

If you're evaluating whether the upgrade is worth it: calculate how many minutes per week you spend manually creating tasks from meeting notes. At 5 minutes per task × 10+ tasks per week = 50+ minutes. The Business plan ($29/month) pays for itself if it saves one hour per month.

What you should see: Your current plan shown with a "Upgrade" option and feature comparison.

Go to Settings → Integrations in the Fireflies dashboard.

For Asana:

1. Click Asana → Connect
2. Authorize Fireflies to access your Asana workspace
3. Select the default Asana project where action items should be created (you can change this per meeting later)
4. Toggle on Auto-create tasks to push action items automatically after every meeting

For Jira:

1. Click Jira → Connect
2. Authorize via Atlassian OAuth
3. Select the default Jira project for action item creation
4. Choose whether Fireflies should create Jira Tasks or Stories for each action item
5. Toggle on Auto-create issues

For Notion:

1. Click Notion → Connect
2. Grant Fireflies access to the relevant Notion workspace
3. Select the Notion database where meeting summaries (and optionally action items) should be logged
4. Configure whether you want a new Notion page per meeting or a running log entry

What you should see: A green checkmark next to the connected integration and a test confirmation message.

Troubleshooting: If the OAuth authorization fails, try connecting from an incognito window with no other Atlassian/Notion sessions open.

For PMs running multiple projects, Fireflies lets you route meeting summaries to different Slack channels based on meeting name or attendee pattern.

Go to Settings → Integrations → Slack. If not already connected, connect your Slack workspace.

Under Routing rules, click Add rule:

• If meeting name contains "ERP Implementation" → Post to channel #erp-delivery
• If meeting name contains "Website Redesign" → Post to channel #web-redesign
• If attendees include [client email domain] → Post to channel #client-[name]
• Default: all other meetings → #general-meeting-notes (or your catch-all channel)

Create one rule per active project. This means your team sees relevant meeting summaries automatically in the right channel without you forwarding them manually.

What you should see: A list of routing rules displayed in the Slack integration settings.

Fireflies has a Task Feed view that consolidates action items from all meetings in one place. Go to the left sidebar and click Tasks.

This view shows every action item Fireflies has captured, across all meetings, with:

• The task description
• Who it's assigned to (as identified from the transcript)
• The meeting it came from (with a link)
• Whether it's been pushed to Asana/Jira or marked complete

Use this as your daily action item review. Every morning, scan the Task Feed for new items from yesterday's meetings and confirm they've been pushed to your PM tool correctly.

What you should see: A consolidated list of open action items across all your projects, sortable by date, meeting, or assignee.

Troubleshooting: If an action item shows the wrong owner (marked as "Unknown" or the wrong person), click the item and manually assign it. Fireflies identifies owners by matching names spoken in the meeting to contacts in your workspace — names not in the system won't auto-assign.

Run a real meeting with the integrations active. After the meeting:

1. Open the Fireflies meeting summary
2. Review the action items section
3. Click each action item to confirm its details are correct
4. Check your Asana/Jira project — the action items should appear as new tasks within 5 minutes of the meeting ending

If a task is missing or wrong:

• Return to the Fireflies meeting view → Tasks tab → manually push the item

What you should see: New Jira tickets or Asana tasks created automatically in your project, with the meeting name in the task description and a link back to the Fireflies transcript.

Once your integrations are running, use this process every Friday morning to accelerate your status report:

1. Open the Meetings view in Fireflies and filter by "This week"
2. Scan the week's meeting summaries — every key decision and commitment is already documented
3. Open the Tasks view and filter by "This week" — this shows every action item created from the week's meetings
4. Copy the completed and in-progress items into your status report template
5. Use ChatGPT to synthesize: paste the week's Fireflies task list + a brief budget/milestone update → prompt ChatGPT to write your status report narrative

This replaces the 2–3 hours of memory-based status report writing with a 30-minute review-and-synthesize process.

What you should see: A populated status report draft in under 30 minutes, built from actual captured data rather than recollection.

Fireflies' AskFred chatbot lets you ask questions across your entire meeting archive. Access it from the sidebar or within any meeting transcript.

You can ask:

• "What did we decide about the budget in the last 3 weeks?"
• "List all open action items assigned to [name] from this month"
• "What risks were discussed in the ERP project meetings this quarter?"
• "When was the go-live date last changed and what was the reason given?"

AskFred searches across all transcripts and returns answers with citations back to the specific meetings where each point was made.

What you should see: An answer with quoted excerpts from the relevant meeting transcripts, with links to jump to the exact moment.