Check version-specific upgrade guidance
When a Linear dependency-upgrade issue changes, Notis consults Context7 for the named package and version transition, reporting migration guidance and breaking changes found.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
Why this helps
Upgrade tasks are risky when guidance for the wrong version gets mixed in.
- Anchors the lookup to the issue’s stated versions
- Highlights documented migration considerations
Setup
Build it in a few focused steps.
- 1Connect Linear and Context7 MCP to Notis in the portal once.
- 2Ask Notis to create an automation, or open Automations → New Automation in the portal.
- 3In one plain-language prompt, say: When a Linear dependency-upgrade issue changes and specifies a package plus source and target versions, resolve the package in Context7 unless an exact library ID is supplied, query version-specific migration guidance and breaking changes, and report only documented findings; skip incomplete upgrades.
- 4Select the Linear trigger, choose a channel for run reports, and create it.
- 5Test with an upgrade issue that explicitly states both versions.
Questions about this workflow
What if the issue omits the target version?
It should report that the version transition is incomplete and wait for the target version rather than mix version guidance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Context7 MCP. A trigger fires from one place; an action lands in another.
Linear triggers
Context7 MCP actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Resolve-library-id
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Not just Linear and Context7 MCP. Any 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 Context7 MCP.