Know How Customers Reacted When You Shipped the Fix
The second an issue closes, Notis fetches customer feedback tied to that fix. See reactions and impact data without hunting through forms.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
You resolve issues but lose track of whether customers are actually happy. Feedback sits in forms you never check until weeks later, if at all.
- See customer reactions the moment an issue resolves
- Reduce time to understand real-world impact
- Avoid context-switching to find feedback forms
- Make data-driven decisions on next priorities
Setup
Build it in a few focused steps.
- 1Connect Linear and Byteforms integrations to Notis.
- 2Ask Notis: 'When an issue is marked as resolved, fetch all feedback forms related to that issue' or configure via the portal.
- 3Set the trigger to 'Issue Updated' (filtering for status = resolved).
- 4Select your notification channel.
- 5Close a test issue and confirm Notis retrieves associated feedback forms.
Questions about this workflow
How does Notis know which feedback forms relate to an issue?
It matches feedback submitted against the issue ID. You can also configure it to pull forms by label or custom fields.
What if no customer feedback exists for an issue?
Notis will notify you that no matching responses were found, so you know to reach out proactively.
Can I set this to only pull feedback for specific issue types?
Absolutely. Tell Notis: 'Only fetch feedback for bug fixes' or 'Only for issues labeled customer-critical'.
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.