Keep documentation lookup aligned with a moved project spec
A file's new path can change the context around it. Recheck the libraries it names with current Context7 docs.
Trigger
Item Moved or Renamed
Triggers when a file or folder is moved to a different path or renamed in OneDrive. Includes both old and new path/name data in the payload.
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
Moved files can lose the context that helped a team find or validate their technical references.
- Revisit documentation when a spec changes location or name.
- Query current docs and code examples from Context7.
- Use old and new path details to orient the review.
Setup
Build it in a few focused steps.
- 1Connect OneDrive and Context7 MCP once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis the outcome in plain language.
- 3In one instruction, ask Notis to review the moved or renamed file's technology references and query Context7 for relevant docs.
- 4Pick the Item Moved or Renamed trigger, choose where run reports go, and test with one real example.
Questions about this workflow
Does a move event include the file contents?
The listed event includes old and new path or name data. The automation may need file access to inspect contents.
Will it infer a new version from the new path?
No. Ask Notis to use a version only if the file or your instruction provides one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link One drive to Context7 MCP. A trigger fires from one place; an action lands in another.
One drive 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.
Onedrivebasetrigger
Base trigger for OneDrive changes using Gmail-style state management. Subclasses override `filter_changes(...)` to extract only the relevant items.
OneDrive File Created Trigger
Triggers when a new file is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
File Updated
Trigger that fires when a OneDrive file's content or metadata changes. Returns file ID, last modified time, and modifier info.
OneDrive Folder Created Trigger
Triggers when a new folder is created in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
OneDrive Item Deleted Trigger
Triggers when a file or folder is deleted in OneDrive. Uses Gmail-style state management for reliable duplicate prevention.
Item Moved or Renamed
Triggers when a file or folder is moved to a different path or renamed in OneDrive. Includes both old and new path/name data in the payload.
Connect any two apps with Notis in the middle.
One drive 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.