Turn Feature Requests Into Structured Forms Automatically
Every new feature request gets a dedicated form capturing scope, user impact, and priority without you lifting a finger.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Create form
Tool to create a new form. use when you need to define and store a form structure.
Why this helps
Feature requests pile up as comments and scattered Slack threads. You manually create forms to gather requirements, then lose track of which feedback belongs where.
- Skip manual form creation for every request
- Capture requirements in structured format immediately
- Keep feature scope and feedback centralized
- Reduce time between request and action
Setup
Build it in a few focused steps.
- 1Connect your Linear workspace and Byteforms account to Notis (one-time setup in the portal).
- 2Ask Notis: 'Create a workflow that generates a requirements form whenever a new feature issue is created in Linear' or use the portal to create the automation.
- 3Set the trigger to 'Issue Created' in Linear.
- 4Choose a Notis channel (Slack, email, etc.) to receive run notifications.
- 5Test by creating a sample feature issue in Linear and verify the form appears in Byteforms.
Questions about this workflow
Can I customize what information the form captures?
Yes. Tell Notis what fields matter: 'Capture user impact, estimated effort, and priority level' and it will reflect that in the auto-generated form.
Will this work for all feature issues or only specific ones?
You can scope it by label or team. For example, 'only create forms for issues labeled product-request' keeps noise down.
What if I don't want a form for every single feature request?
Tell Notis your rule: 'Only create forms for high-priority feature requests' or 'Skip forms if the issue already has customer quotes'.
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.