Skip to content
Notis

Keep compliance research moving on a schedule

Set a recurring prompt for the libraries and topics your 21risk reviews cover, and get a fresh documentation lookup in your report channel.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

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

Compliance research can stall when nobody has time to revisit the relevant technical documentation before a review.

  • Put a recurring documentation lookup on the calendar you choose.
  • Focus each run on the libraries, versions and topics you specify.
  • Keep lookup results in a chosen report channel for review.

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 recurring compliance references.
  • 3In one instruction, specify the libraries, versions and compliance topics to look up, and ask Notis to resolve each library before querying current Context7 documentation.
  • 4Pick the notis_cron trigger, set the recurring schedule, and choose where run reports should go.
  • 5Run one real example with a review topic and confirm the references are useful.

Questions about this workflow

Can this detect changes since the last run?

No. The available action retrieves and queries current documentation, but no history or change-detection capability is specified.

Where do the compliance topics come from?

Provide them in the automation instruction or its run context. The workflow cannot infer topics or baselines that were not supplied.

Does the schedule trigger a 21risk event?

No. The trigger is a Notis schedule. No 21risk trigger event is provided.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.