Keep Linear issues current with scheduled browser checks
A recurring browser check can bring the latest observed status back to the Linear issue, so you do not have to remember to revisit the page yourself.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Follow-up checks are easy to forget, and the latest state of a website flow can remain buried in browser history instead of the issue.
- Bring periodic observations back into the issue discussion.
- Keep the check result and its run context together for teammates.
- Reduce memory load around recurring web follow-up.
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, name the page or flow and Linear issue, and ask Notis to inspect it with Browserless and comment with the observed status, timestamp, and relevant evidence.
- 4Choose the notis_cron trigger and select where run reports should go.
- 5Test with one real page check and confirm the comment is useful on the issue.
Questions about this workflow
What starts this workflow?
A recurring schedule starts the automation. Choose the cadence that fits how often the page or flow needs review.
What should I provide in the instruction?
Name the page or flow to inspect and identify the existing Linear issue where the result belongs. The automation needs enough context to find the right issue.
Does this guarantee the page works for every user?
No. The comment reports what Browserless observed during that run. It is a point-in-time check, not a guarantee across environments or users.
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.