Keep Jira issues aligned with meeting decisions
When a discussion changes the plan, carry the decision into the Jira issue while the context is fresh.
Trigger
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
Ticket descriptions and plans can fall out of date after meetings, leaving teams to work from stale information.
- Reflect explicit meeting decisions in Jira issue details.
- Keep current plans visible where work is tracked.
- Avoid relying on memory to update ticket context after a call.
Setup
Build it in a few focused steps.
- 1Connect Fireflies and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, or ask Notis in any channel.
- 3Tell Notis to update an existing Jira issue only when the transcript contains an explicit decision that changes its details.
- 4Pick Fireflies Transcription Complete as the trigger and select a run report destination.
- 5Test with a completed transcript that discusses a known Jira issue and review the edit.
Questions about this workflow
Will this change an issue after any mention?
Instruct Notis to require an explicit decision that changes the issue details, and to skip unclear mentions.
Which issue fields can it update?
The Jira edit action supports issue field updates. Specify the intended details in your instruction, such as a revised description or priority.
Can it also add context about the decision?
Ask Notis to include the decision in the updated issue description when that is useful.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Jira. A trigger fires from one place; an action lands in another.
Fireflies triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Fireflies and Jira, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.