Feedback Automatically Organized and Categorized
Feedback gets categorized automatically. No manual organization of customer insights.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Update Amplitude Event Category
Update an existing event category in amplitude. this action allows you to: - update the name of an existing event category - validate the new category name key features: - updates category names - returns success/failure status
Why this helps
Customer feedback arrives unorganized in Linear comments and requires manual categorization, creating cognitive overhead and often gets skipped.
- Feedback automatically categorized
- No manual organization work
- Insights structured for analysis
- Reduced cognitive load
Setup
Build it in a few focused steps.
- 1Connect Linear and Amplitude to Notis.
- 2Create an automation: 'When a comment is added, analyze its content and automatically update or create the appropriate Amplitude event category for that type of feedback.'
- 3Set the trigger to 'Comment Received'.
- 4Choose your notification channel.
- 5Test by adding a feedback comment and verify Amplitude categories are updated to reflect the feedback type.
Questions about this workflow
How does Notis categorize feedback?
Notis uses AI to analyze comment content and assign it to logical categories (e.g., feature request, bug report, UX feedback). You can guide this by specifying category rules in your instruction.
What if feedback doesn't fit existing categories?
Your automation can create new categories as needed. Specify 'create category if needed' in your instruction and Notis will organize it appropriately.
Can I exclude certain feedback from categorization?
Yes. Your instruction can specify filters like 'only categorize customer feedback' or 'exclude team comments' to focus on relevant feedback.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Amplitude. A trigger fires from one place; an action lands in another.
Linear triggers
Amplitude actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Amplitude Cohort Status
Check the status of a cohort export request. this action allows you to: - poll the status of an in-progress cohort download request - determine if a cohort is ready for download
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Amplitude Event Category
Create a new event category in amplitude. this action allows you to: - create a new event category to organize event types - validate category name before creation key features: - creates event categories for organizing events - returns success/failure status
Comment Received Trigger
Triggered when a comment is received.
Create Amplitude Event Type
Create a new event type in amplitude. this action allows you to: - define a new event type with various properties - associate the event with a category - add metadata like description, tags, and owner key features: - creates trackable events in your amplitude project - supports full event type configuration
Issue Created Trigger
Triggered when a new issue is created.
Delete Amplitude Event Category
Delete an event category from amplitude. this action allows you to: - delete an existing event category - remove category organization from events key features: - permanently removes event categories - returns success/failure status
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Amplitude Event Type
Delete an event type from amplitude. this action allows you to: - remove an event type from your project - mark live events as deleted - remove planned events from the tracking plan key features: - different behavior based on event status (live, planned, etc.) - returns success/failure status
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).
Request Amplitude Cohort
Get a single cohort by id and initiate download. this action allows you to: - request a specific cohort from amplitude - optionally include user properties in the response - start the asynchronous download process key features: - supports filtering by specific user properties - returns a request id used for polling status and downloading - supports eu data residency
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Amplitude Event Categories
Get event categories from amplitude. this action allows you to: - get all event categories in your project - get a specific category by name
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Amplitude Event Type
Get a specific event type from amplitude by name. this action allows you to: - retrieve detailed information about a single event type - get all properties and metadata for the event key features: - retrieves comprehensive event type details - returns metadata like category, description, and settings - supports lookup by exact event name
Connect any two apps with Notis in the middle.
Linear and Amplitude, 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 Amplitude.