Update Linear issue details when Botster results confirm a condition
Let evidence from a collection run move the related work forward, using the condition and issue you specify in the automation instruction.
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
Teams can leave completed or newly validated work in an outdated issue state after a data collection run.
- Reflect validated findings in the existing issue.
- Reduce manual follow-up after a relevant collection run.
- Keep issue changes tied to a stated evidence condition.
Setup
Build it in a few focused steps.
- 1Connect Botster and Linear once in Notis.
- 2Create an automation in the portal or from any channel.
- 3In one instruction, identify the Linear issue, state the evidence condition, and describe the permitted update.
- 4Choose a webhook as the trigger and select where run reports should go.
- 5Test with one real result and verify the issue details changed as intended.
Questions about this workflow
Can this change a Linear issue state?
The Update issue action supports issue updates, including state, when the required valid state id is available. Specify the intended outcome clearly.
What if the Botster result does not meet the condition?
Describe that Notis should leave the issue unchanged when the evidence does not meet your condition.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botster to Linear. A trigger fires from one place; an action lands in another.
Botster 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.
Botster 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.