Surface Blockers the Moment They're Mentioned
Team mentions a blocker in comments? Notis auto-retrieves your blocker tracking form and adds it to the queue so nothing slips through.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
Why this helps
Blockers get mentioned casually in Linear comments and never tracked. Work stalls without anyone realizing why.
- Catch and track blockers before they become crises
- Keep blocker queue visible and prioritized
- Reduce work stalls by surfacing impediments
- Build data on what blocks your team most
Setup
Build it in a few focused steps.
- 1Connect Linear and Byteforms to Notis.
- 2Tell Notis: 'When a comment mentions a blocker or impediment, retrieve my blocker tracking form and add this to the list' or use the portal.
- 3Set the trigger to 'Comment Received'.
- 4Choose your notification channel.
- 5Post a comment mentioning a blocker and verify Notis retrieves your blocker form.
Questions about this workflow
How does Notis detect that a comment mentions a blocker?
It looks for keywords like 'blocked', 'waiting on', 'can't proceed', or phrases you teach it to recognize.
Can it automatically update the blocker's priority based on context?
Yes. Tell Notis: 'Blockers mentioned in high-priority issues get marked urgent'.
Should blockers auto-assign to someone for resolution?
You can tell Notis: 'Route blockers to the person mentioned or the issue lead' to avoid assignment limbo.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Byteforms. A trigger fires from one place; an action lands in another.
Linear triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
Comment Received Trigger
Triggered when a comment is received.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
Issue Created Trigger
Triggered when a new issue is created.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Byteforms, 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 Byteforms.