Catch cycle slippage before the sprint ends
Finding out a cycle is off track on the last day helps no one. Notis pulls the cycles for your Linear team on a midweek schedule and sends a progress check, so there is still time to adjust when it counts.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get cycles by team ID
Retrieves all cycles for a specified linear team id; cycles are time-boxed work periods (like sprints) and the team id must correspond to an existing team.
Why this helps
Cycle health is easy to ignore until the retro, by which point it is too late to change the outcome.
- You see how the current cycle is tracking while there is still time to act.
- A midweek rhythm turns cycle health into a habit, not a retro surprise.
- Course-corrections happen during the sprint instead of after it.
Setup
Build it in a few focused steps.
- 1Connect Linear to Notis once through the portal.
- 2Ask Notis for your portal link and create a New Automation, or set it up conversationally.
- 3Write one instruction, for example: Every Wednesday, pull the cycles for my Linear team and send me a progress check.
- 4Pick a recurring midweek schedule as the trigger.
- 5Choose the channel for the check and run it once to confirm.
Questions about this workflow
Which team's cycles does it read?
The team you name in your instruction. Notis retrieves the cycles for that team and reports on them.
Does it need a Jira event?
No. It runs on the schedule you set and reads only Linear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Linear. A trigger fires from one place; an action lands in another.
Jira triggers
Linear actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
New Project
Triggered when a new project is added in Jira
Create a comment
Creates a new comment on a specified linear issue.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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 Jira and Linear. Any combination from 1,000+ 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.