Turn a documentation request into a Context7 library ID
Submit the library name and let Notis find its Context7-compatible identifier before the docs search.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
A useful documentation request can stall when the exact Context7 library ID is unknown.
- Accept documentation requests through an HTTP trigger.
- Resolve a package or product name before querying docs.
- Return candidate matches for a person to confirm when ambiguous.
Setup
Build it in a few focused steps.
- 1Connect 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 resolve the library name provided with each request and report candidates when the match is ambiguous.
- 4Pick the webhook trigger, choose where run reports go, and test with one real example.
Questions about this workflow
What starts the automation?
An HTTP request to the Notis webhook starts it. Include the library or product name in the request context.
Does it fetch docs after resolving?
No. This workflow uses Resolve-library-id. A separate query-docs automation can retrieve the documentation.
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.