Bug Calls Become Linear Issues Instantly
Your team discusses a bug in Fireflies. A detailed Linear issue appears automatically with reproduction context and next steps.
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
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Why this helps
Your team has a call about a bug, but someone has to manually create the Linear issue, type up what was discussed, and add context. Details get lost, and the bug lingers undocumented.
- Bug discussions are documented in Linear within minutes of the call.
- Reproduction steps and context are captured automatically, not typed later.
- Engineers see the full discussion without rewinding the call.
Setup
Build it in a few focused steps.
- 1Connect Fireflies and Linear to Notis.
- 2Create an automation: 'When a Fireflies call completes and mentions a bug (e.g., contains keywords like "bug", "error", or "broken"), create a Linear issue in the Bug team and include reproduction steps from the discussion.'
- 3Test with a recorded bug discussion call to ensure the issue captures key details.
- 4Optionally configure Linear fields like priority and cycle based on urgency keywords in the call.
- 5Refine keyword filters if you're catching too many or too few bug calls.
Questions about this workflow
How does Notis identify a bug discussion vs. a regular call?
Your prompt defines it. Common triggers are keywords in the call ('bug', 'error', 'crash') or meeting titles that mention bugs. You can also specify attendees (e.g., 'if the engineering lead is present').
Can Notis extract exact error messages or stack traces?
If they're mentioned in the call or shared by participants, Notis can include them in the issue description.
Should this create a separate issue for each bug or one issue per call?
You can ask Notis to create one issue per distinct bug mentioned, or one issue per call with a summary. Choose what works for your team.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Linear. A trigger fires from one place; an action lands in another.
Fireflies triggers
Linear actions
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.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Create a comment
Creates a new comment on a specified linear issue.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Not just Fireflies and Linear. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.