Carry Checkvist priority changes into Linear
When a task's urgency changes, pass the context to Notis and update the related Linear issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update issue
Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.
Why this helps
Priority changes recorded in a task list can leave the related team issue showing stale urgency.
- Bring a task's changed priority context into a specified issue.
- Reduce stale urgency information across work tools.
- Keep the Linear issue description or priority current as directed.
Setup
Build it in a few focused steps.
- 1Connect Checkvist and Linear once in the Notis portal.
- 2Create an automation in Automations, New Automation, or ask Notis in plain language.
- 3In one instruction, tell Notis how to use the provided Checkvist task context to update a specified existing Linear issue, and which issue attribute to change when the context supports it.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real task and its specified Linear issue.
Questions about this workflow
Does Checkvist provide a built-in priority-change event?
No Checkvist trigger events are listed for this workflow. A Notis webhook starts the run, with task context supplied for Notis to process.
Can Notis update any Linear issue?
The workflow should identify a specified existing issue and provide a valid value for the attribute to change. The update action requires an issue id and at least one attribute.
What if the task context does not say what changed?
Ask Notis to skip the update when the provided context does not support a clear change. The automation should not invent a new priority.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Checkvist to Linear. A trigger fires from one place; an action lands in another.
Checkvist triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Checkvist and Linear, 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 Linear.