---
title: "How to get AI meeting notes into Jira automatically"
canonical: https://candor.inc/integrations/meeting-notes-to/jira
author: Sarthak Singh, co-founder of Candor
date_published: 
date_modified: 
---

# How do I get AI meeting notes into Jira automatically?

Fireflies' native Jira integration creates issues from meeting action items automatically after each meeting, with the owner, time mentioned and a recording link. Read AI creates issues when you click, on Pro, Enterprise or Enterprise+, per its Jira help page. Otter and MCP assistants act only when asked, while Granola and Fathom document Zapier routes.

We haven't run this test yet. Where a table shows a product's behaviour, it's what that product's maker says, checked on 4 November 2026.

Disclosure: Candor is an app that will compete with some products named here. We describe every product, including Candor, from its own documentation, and we'll test them all with the same published method.

> **Short answer**
> - Fireflies documents automatic issue creation from meeting action items, with an owner, mention time and link to the recording. [1]
> - Otter Work can create Jira tickets from meeting follow-ups when you ask; some actions wait for your approval. [5]
> - Read AI and Fellow create issues from action items after you click. Read requires Pro, Enterprise or Enterprise+; Fellow does not state a plan requirement. [2] [3] [4]
> - Granola and Fathom document Zapier paths. Circleback has Zapier and Make automations; tl;dv lists Zapier, but its Jira-specific fields and plan are not verified. [6] [8] [9] [10] [11] [12]

## Which meeting note takers connect to Jira natively?

Here, “native” means the note app itself has a Jira connection. It does not mean every tool sends notes in the background.

| Notetaker | What happens | What the vendor says gets sent | Plan requirement |
|---|---|---|---|
| Fireflies | Automatic issue creation from meeting action items. By default, data from every meeting can go to Jira; filters can narrow it. | Action item or next step, owner, time mentioned, and a link to the full recording. You pick the Jira project and issue type. | The Jira guide does not state a minimum plan. Integration Rules are Business or higher. [1] |
| Otter | Prompt Otter AI Chat in Work mode to create Jira tickets from meeting follow-ups. It may ask permission before taking an action. | The guide describes ticket creation but does not specify which meeting fields appear in the issue. | Not verified. The current guide does not give a plan matrix for Jira Work. [5] |
| Read AI | Click the Jira control beside an action item in a meeting report, then create the issue. | Action item text is prefilled in Description; Read pulls project and issue type fields from Jira and links back to the Read report. | Pro, Enterprise or Enterprise+. [2] [3] |
| Fellow | Push an action item to Jira from meeting notes; bring Jira issues into agendas. Status updates can flow both ways. | Assignee, due date and a link to the original meeting note. | Not stated on the Jira page. [4] |
| Notion AI Meeting Notes | A Notion AI Connector for Jira appears in Notion's Connections directory. That directory entry does not document sending a meeting note or action item into a Jira issue. | Meeting-notes-to-issue behavior: Not verified. | Notion says AI Meeting Notes requires Business or Enterprise, with eligible mobile subscriptions also supported. [13] [14] |

The useful difference is who starts the transfer. Fireflies is the only source here that documents a meeting-triggered push. Read and Fellow wait for someone to choose an action item. Otter Work waits for a request, and may wait for approval too. Treat an automatic push like a conveyor belt: decide which items belong on it before you switch it on.

## What can you use when the note app has no native Jira push?

**Zapier or Make.** These tools pass a trigger from the note app to a Jira action. Granola's directory lists Jira via Zapier, with a recipe that turns meeting action items into Jira issues; its pricing page places Zapier among Business integrations. Fathom says its Zapier connection can send summaries, highlights and action items to other apps. Its help page lists personal-use Zapier on Free and Premium. [6] [7] [8] [9]

Circleback lists Zapier, Make, webhooks and an API for meeting outcomes. Its pricing page says automations with all integrations start on Pro. The directory does not name Jira as a direct Circleback integration, so check the specific Zapier or Make trigger and destination fields before building around it. tl;dv's help center lists a Zapier integration, but the page opened here does not establish which meeting fields can trigger a Jira issue or which plan includes that flow. [10] [11] [12]

A Zap is like a mailroom rule: a new meeting event arrives, the rule copies selected fields onto a Jira issue form, and Jira stores that issue. Map the meeting title to Summary, the action item to Description, and the project and issue type to values Jira accepts. Add the source meeting link to the description if the note app exposes one. Do not assume a connector sends a full transcript; the documented payloads above are action items or selected summary fields.

**MCP through an AI assistant.** Atlassian's MCP server includes a `createJiraIssue` tool. You can connect it to an AI client, give the client a meeting note or a note app that exposes the relevant content, and ask it to create tickets. That is an assistant-run action, not an event-triggered sync; the client can only use the tools and permissions you grant it. Meeting content access and plan requirements vary by note app, so check those separately. [15] [16]

## What goes into Jira, and where can it go wrong?

| Transfer method | Payload the vendor documents | Direction and control |
|---|---|---|
| Fireflies | Action items, owner, mention time and recording link. | Fireflies creates Jira issues. The assigned-to-me filter limits which issues it creates; Integration Rules can limit which meetings send data. [1] |
| Otter Work | Jira tickets from meeting follow-ups; exact ticket fields are not verified. | You ask Otter to act. Some actions need approval. [5] |
| Read AI | One action item's text in Description, Jira fields you fill, and a link to the Read report. | User-triggered create action. Jira-required fields must be filled. [2] |
| Fellow | Action item, assignee, due date and note link. Existing tickets can be imported, with status updates in both directions. | User pushes action items; Jira and Fellow status updates can sync both ways. [4] |
| Zapier / Make | Depends on the source trigger and fields it exposes. Fathom documents summaries, highlights and action items; Granola documents action items to Jira issues. | Set the trigger, mapping and Jira create-issue action yourself. [6] [8] [10] [11] |

Three setup choices prevent most bad tickets:

1. **Filter before creating.** Fireflies sends data from every meeting by default. Turn on its assigned-to-me filter or add Integration Rules for selected meetings if only a subset belongs in Jira. [1]
2. **Map required fields.** Read AI's help page says it pulls the fields for the Jira project and issue type you choose, and it will not let you create an issue until required fields have values. Apply the same check to a Zap or Make scenario: project, issue type and any required custom fields need real values. [2]
3. **Check retries and duplicates.** The vendor pages reviewed do not promise duplicate detection when the same meeting or action item is processed twice. Before enabling a broad trigger, send one test meeting, retry it, and inspect whether Jira creates a second issue.

## How do you set up a Jira sync?

### Fireflies automatic issue creation

1. In Fireflies, open **Integrations**, find Jira and select **Connect**.
2. Sign in to Atlassian and accept the requested permissions.
3. In **Default Configuration**, choose the Jira project and issue type.
4. Enable the assigned-to-me filter if you want Fireflies to create only issues assigned to you during the meeting.
5. Add Integration Rules for selected meetings if your plan includes them, then save the configuration. [1]

### Read AI issue creation

1. Connect Jira from Read's **Integrations** page and authorize access in Atlassian. A workspace admin may need to enable it first.
2. In a meeting report, hover over an action item and choose the Jira icon.
3. Review the project, issue type and required Jira fields, edit the description if needed, then create the issue. Read's help page says Read adds a link back to the meeting report. [2]

### Zapier or Make

1. Pick a source event that fires when the meeting or action item is ready, not when the meeting starts.
2. Add Jira's create-issue action and choose a project and issue type.
3. Map only the fields you want to keep. Put the action item in the issue body and add the meeting link if the source provides one.
4. Run a single test, inspect the Jira issue, then check what happens if the source event is replayed. Save and enable the automation only after those fields look right.

## What this page can't tell you

- Whether an integration creates the same issue reliably on every meeting. We haven't run any of these products for this page.
- Whether Fireflies, Otter or Fellow deduplicate repeated action items, or how each handles a meeting that is reprocessed. The reviewed vendor pages do not say.
- Whether tl;dv's Zapier route exposes the right trigger and fields for a Jira issue, or which plan includes that exact route.
- Which fields Otter Work writes into Jira, and which plan currently includes that Jira action.
- Whether a note app's MCP connector exposes all meeting text, action items or a recording link to an assistant. The Jira write tool alone cannot fetch notes from a separate app.

## Frequently asked questions
### Can an AI meeting notetaker turn action items into Jira tasks?

Yes, Fireflies documents automatic Jira issue creation from meeting action items. Read AI (per its help page) and Fellow also create issues, but require someone to choose the action items. [1][2][3][4]

### Can I send a meeting summary or transcript to Jira?

You can send selected meeting content through a Zapier or Make workflow, depending on the app and fields it exposes. The page does not document a general full-transcript sync to Jira. [6][8][10][11]

### Does Read AI need a paid plan for Jira?

Yes, Read AI lists Pro, Enterprise or Enterprise+ for its Jira integration. Its help page says you create an issue by clicking the Jira control beside an action item in a meeting report. [2][3]

### Can Google Meet notes automatically create Jira tickets?

The page does not document a direct automatic Google Meet to Jira sync. It describes assistant-run Jira issue creation through Atlassian MCP, while Fireflies documents automatic issue creation from meeting action items. [1][15][16]

## About this page

Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at [candor.inc/docs](https://candor.inc/docs).

<!-- candor:about start -->
Candor doesn't export to Jira directly; you can copy the Summary, Notes or Transcript, post to Slack, or share a web link with Copy Link ([Copy and share meeting notes](https://candor.inc/docs/meetings/playback-and-export#copy-content-into-another-app)). Candor's docs on this page's topic: [Copy and share meeting notes](https://candor.inc/docs/meetings/playback-and-export).
<!-- candor:about end -->

Last checked: 4 November 2026. To report an error, email support@candor.inc.

## Sources

1. Fireflies Knowledge Base, How to integrate Jira with Fireflies — https://guide.fireflies.ai/articles/6214483081-how-to-integrate-jira-with-fireflies — checked 2026-11-04
2. Read Help Center, Connecting your Read account to Jira — https://support.read.ai/hc/en-us/articles/34204676394643-Connecting-your-Read-account-to-Jira — checked 2026-11-04
3. Read AI plans and pricing — https://www.read.ai/plans-pricing — checked 2026-11-04
4. Fellow, Jira integration — https://fellow.ai/integrations/jira — checked 2026-11-04
5. Otter Help Center, Otter AI Chat Overview — https://help.otter.ai/hc/en-us/articles/19682180167575-Otter-AI-Chat-Overview — checked 2026-11-04
6. Granola integrations — https://www.granola.ai/integrations — checked 2026-11-04
7. Granola pricing — https://www.granola.ai/pricing — checked 2026-11-04
8. Fathom integrations — https://www.fathom.ai/integrations — checked 2026-11-04
9. Fathom Help Center, Free vs. Premium for Individuals — https://help.fathom.video/en/articles/5290881 — checked 2026-11-04
10. tl;dv Help Center, Integrations — https://intercom.help/tldv/en/collections/3324425-integrations — checked 2026-11-04
11. Circleback integrations — https://circleback.ai/integrations — checked 2026-11-04
12. Circleback pricing — https://circleback.ai/pricing — checked 2026-11-04
13. Notion Connections directory — https://www.notion.com/connections — checked 2026-11-04
14. Notion Help, Take AI Meeting Notes in Notion — https://www.notion.com/help/ai-meeting-notes — checked 2026-11-04
15. Atlassian Support, Get started with the Atlassian MCP server — https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server — checked 2026-11-04
16. Atlassian Support, Supported tools — https://support.atlassian.com/atlassian-ai-gateway/docs/supported-tools/ — checked 2026-11-04