Turn a library name in a calendar event into a Context7 library ID
Capture the exact Context7-compatible library ID for a package mentioned in a new technical event, ready for a later documentation lookup.
Trigger
Event Created
Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.
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
Package names and Context7 library IDs do not always match, which can slow down documentation research.
- Resolve names to Context7-compatible IDs as events are created.
- Keep the resolved ID with the run report for easy follow-up.
- Avoid guessing the identifier format.
Setup
Build it in a few focused steps.
- 1Connect Google Calendar and Context7 in the Notis portal once.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to inspect each new event for a library or framework name and use Context7 to resolve its compatible library ID.
- 4Pick Event Created as the trigger and choose where run reports should go.
- 5Test with one real event containing a supported package name.
Questions about this workflow
Does this retrieve the documentation too?
This workflow resolves the library ID. To retrieve documentation, use a separate Context7 Query-docs action after a compatible ID is available.
What if an event mentions several libraries?
In your instruction, ask Notis to resolve each clearly named library and report any ambiguous matches.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Calendar to Context7 MCP. A trigger fires from one place; an action lands in another.
Google Calendar 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.
Attendee Response Changed
Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.
Event Canceled or Deleted
Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.
Event Starting Soon
Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.
Calendar Event Changes
**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).
Event Created
Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.
Calendar Event Sync
Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).
Connect any two apps with Notis in the middle.
Google Calendar 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.