Give parsed email technology names an exact identity
Make downstream documentation lookups dependable from the start.
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
Automation pipelines fail when a parsed email name does not map cleanly to a package or framework.
- Improves downstream lookup quality
- Flags ambiguous names early
- Works with existing parsers
Setup
Build it in a few focused steps.
- 1Connect Outlook and Context7 MCP in the Notis portal.
- 2Create an automation that accepts parsed message text through a Notis webhook.
- 3Tell Notis to extract technology names, resolve each Context7 library ID, and return confidence notes and unresolved names.
- 4Choose a Notis webhook trigger and select a report channel.
- 5Send one parsed Outlook payload to test it.
Questions about this workflow
Can the parser send several messages at once?
Yes. Tell Notis how to separate messages and return one resolution result per message.
What if the name is a company product?
Context7 may return product documentation matches, or mark the name unresolved when no suitable library exists.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Outlook to Context7 MCP. A trigger fires from one place; an action lands in another.
Outlook 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.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Connect any two apps with Notis in the middle.
Outlook 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.