Keep verified feedback answers out of scattered notes
When a new Linear issue records a completed customer follow-up, ask Notis to save the confirmed answers as a Formbricks survey response.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Create Survey Response
Tool to create a response for a survey. Use after collecting all survey answers.
Why this helps
Feedback collected during a conversation can remain in issue text or notes instead of the survey dataset used for analysis.
- Keep confirmed feedback available in the survey response record.
- Reduce duplicate data entry after customer conversations.
- Make it easier to include follow-up feedback in later analysis.
Setup
Build it in a few focused steps.
- 1Connect Linear and Formbricks to Notis once through the portal.
- 2Create an automation prompt that explains how to identify a completed follow-up and its confirmed survey answers.
- 3Select the Linear Issue Created trigger and choose where run reports should appear.
- 4Test with one real issue containing verified answers and check the Formbricks response.
Questions about this workflow
Will this invent missing survey answers?
The prompt should instruct Notis to use only confirmed answers and avoid creating a response when required information is missing.
What does the Formbricks action require?
It creates a response after the survey and its answers are known.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Formbricks. A trigger fires from one place; an action lands in another.
Linear triggers
Formbricks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Action Class
Tool to create a new action class. Use when defining custom action logic in your environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Attribute Class
Tool to create an attribute class in Formbricks. Use when you need to define new attribute classes for segmentation or attributes management.
Comment Received Trigger
Triggered when a comment is received.
Create Contact
Tool to create a new contact. Use when you need to register a contact in a Formbricks environment.
Issue Created Trigger
Triggered when a new issue is created.
Create Display
Tool to mark a survey as displayed or link it to a response. Use after obtaining the survey and environment IDs to register a display instance.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Survey Response
Tool to create a response for a survey. Use after collecting all survey answers.
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).
Create Survey
Tool to create a new survey. Use after defining survey details and questions.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create Webhook
Tool to create a new webhook. Use when you need to register an external endpoint to receive form response events.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Delete Attribute Class
Tool to delete an attribute class. Use when you need to remove an attribute class by its ID after confirming it's no longer needed.
Connect any two apps with Notis in the middle.
Linear and Formbricks, 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 Formbricks.