Get documentation for a 21risk finding
Give Notis the finding and the library or framework involved. It can look up current Context7 documentation and examples to help you plan a fix.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 risk finding can leave you switching between audit notes, search results and documentation before you can decide what to change.
- Get relevant documentation alongside the finding that prompted the research.
- Request guidance for the versions named in the webhook payload.
- Receive source-backed code examples when the documentation provides them.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Context7 MCP once in the Notis portal.
- 2Create an automation in Notis and name it for risk finding documentation.
- 3In one instruction, ask Notis to use the finding details and stated technology to resolve the library, then retrieve relevant Context7 documentation and examples.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Send one real finding with its library and version details to test the result.
Questions about this workflow
Does this run automatically when a 21risk finding is created?
No 21risk trigger event is provided here. The workflow starts when its Notis webhook receives an HTTP request.
What information should I include?
Include the finding, relevant checklist or audit context, the library or framework, and its version if known. Notis can only tailor the lookup to information supplied.
How does Context7 identify the library?
The workflow first resolves the package or product name to a Context7-compatible library ID, then queries documentation with that ID.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Context7 MCP. A trigger fires from one place; an action lands in another.
21risk 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.
Connect any two apps with Notis in the middle.
21risk 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.