Keep documentation research aligned with task changes
When implementation details change, refresh the documentation lookup from the task's latest context.
Trigger
Task Updated
Triggers when a task is updated in a project.
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
A changed requirement can make earlier research stale, while nobody remembers to repeat the documentation search.
- Base each lookup on the task's current details.
- Make changed version or library context part of the new research.
- Reduce stale links and examples during implementation.
Setup
Build it in a few focused steps.
- 1Connect Asana and Context7 MCP once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to use the latest task details, resolve the named library ID first, then query Context7 for documentation relevant to the updated question.
- 4Pick the Asana Task Updated trigger for the relevant project.
- 5Choose a report channel, then test with one real task update that changes its technical question or version.
Questions about this workflow
Will it know what changed?
It can analyze the latest task data available to it. A prior task version or change history is not guaranteed by the listed event, so supply that baseline if you need a comparison.
Can it avoid querying when the update is unrelated?
Describe the desired decision in your instruction and ask Notis to query only when the available task details contain a documentation question.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Context7 MCP. A trigger fires from one place; an action lands in another.
Asana 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.
Attachment Added to Task
Triggers when an attachment is added to a task.
New Comment on Task
Triggers when a comment is added to a task in a project.
New Task Created
Triggers when a new task is created in a project.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Task Updated
Triggers when a task is updated in a project.
Connect any two apps with Notis in the middle.
Asana and Context7 MCP, 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 Context7 MCP.