Track Every Feature Development Task Automatically
Stop manually logging development work. Every Linear issue becomes a tracked analytics event.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Send Events to Amplitude
Send events to amplitude using the http v2 api. this action allows you to send events to amplitude for tracking user behavior and analytics. it supports all amplitude event fields, handles proper validation, and includes comprehensive error handling.
Why this helps
Manually logging feature development requires context-switching between tools and gets forgotten, causing analytics to miss critical product work data.
- Zero manual work logging needed
- All feature development automatically tracked
- No cognitive overhead for data entry
- Never miss tracking a development task
Setup
Build it in a few focused steps.
- 1Connect your Linear and Amplitude accounts to Notis via the portal (one-time setup).
- 2In Notis, create a new automation by telling it: 'When a new issue is created in Linear, send an event to Amplitude with the issue title and description.'
- 3Select 'Issue Created Trigger' from Linear as your automation trigger.
- 4Choose your Notis channel (Slack, email, etc) for run notifications.
- 5Test by creating one new issue in Linear and verify it appears in Amplitude within seconds.
Questions about this workflow
Will this track all issues or only certain ones?
This automation triggers on every new issue. You can refine it later to only track issues with specific labels or in specific projects by updating the plain-language instruction.
What data gets sent to Amplitude?
The automation sends the issue title, description, assignee, priority, and status. Notis interprets your instruction to include or exclude fields as needed.
Can I track issue updates too, not just creation?
Yes. Create a separate automation for 'When an issue is updated' to track all changes. Many teams run both.
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.