Verify a web fix and update its Linear issue
When a fix is ready to revisit, send a recheck request to Notis. Browserless inspects the flow, and the existing Linear issue gets the observed result.
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
After a web fix ships, someone still has to reopen the flow, verify it, and bring the evidence back to the issue.
- Bring a post-fix browser observation into the existing issue.
- Keep verification evidence close to the issue being resolved.
- Avoid reopening the same context and manually rewriting the result.
Setup
Build it in a few focused steps.
- 1Connect Browserless and Linear once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, ask Notis to use the supplied Linear issue context and page or flow details to recheck the reported fix with Browserless, then update the issue with the observed result and evidence.
- 4Choose the notis_webhook trigger and select where run reports should go.
- 5Test with one real issue and a page or flow that can be safely rechecked.
Questions about this workflow
What starts a recheck?
A Notis webhook starts it when an HTTP request is sent. The request should provide the issue and enough information to identify the page or flow.
What does the issue update represent?
It records the result Browserless observed in that run. Notis should not mark a fix as verified if the check was inconclusive or the needed page context was missing.
Can this recheck any kind of Linear issue?
It is useful when an issue describes a web page or flow that Browserless can inspect. Issues without a browser-checkable outcome need another verification method.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserless to Linear. A trigger fires from one place; an action lands in another.
Browserless 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.
Browserless 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.