Turn Feature Discussions Into Quantified Voting Data
Feature discussion happening in Linear comments? Notis creates a voting form instantly capturing interest and reasoning from all participants.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Create form
Tool to create a new form. use when you need to define and store a form structure.
Why this helps
Feature votes get scattered across comments. You can't easily see who wants what or why, making prioritization a guessing game.
- Quantify feature interest instead of guessing
- Capture reasoning behind votes for better decisions
- Build visible consensus so priorities feel fair
- Make data-driven roadmap decisions
Setup
Build it in a few focused steps.
- 1Connect Linear and Byteforms to Notis.
- 2Ask Notis: 'When a comment mentions a feature or is posted on a feature-request issue, create a feature voting form asking if people want this and why' or use the portal.
- 3Set the trigger to 'Comment Received' (on feature discussion or feature-request labeled issues).
- 4Select your notification channel.
- 5Comment about a feature in Linear and verify the voting form appears in Byteforms.
Questions about this workflow
Can the form weight votes by role (e.g., customer votes count more)?
Yes. Tell Notis to tag votes by role so you can analyze customer vs internal interest separately.
What if the same feature gets discussed multiple times?
Tell Notis to consolidate votes into one form per feature, or create separate rounds if timing matters.
Can the form include a free-text field for reasoning?
Absolutely. Include 'Why is this feature important to you?' so you get the story behind votes.
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.