Keep an accurate read on your Linear roster
Assignments only work when they land on active people, and rosters drift as folks join or go quiet. Notis lists your Linear users on a weekly schedule, so you always know who is really there before you plan.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Linear users
Lists all users in the linear workspace with their ids, names, emails, and active status.
Why this helps
Assigning work to someone who has gone inactive is a silent way to lose it, and nobody notices until the deadline slips.
- You get a current view of who is in Linear before planning or assigning.
- Inactive members surface before work quietly lands on them.
- A weekly rhythm keeps the roster picture fresh without a manual audit.
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 in plain language.
- 3Write one instruction, for example: Every Friday, list the users in my Linear workspace and flag who is active.
- 4Pick a recurring weekly schedule as the trigger.
- 5Choose the channel for the report and run it once to confirm.
Questions about this workflow
Does this change anything in Linear?
No. It reads your workspace users and reports them to you. It makes no edits.
Can I get email addresses too?
Yes. The user list includes names, emails, and active status, and you can ask Notis to include what you need.
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.