Keep the right Context7 library ID within reach
For teams that revisit Adtraction integration work over time, schedule a library lookup using the package name you maintain and get the compatible Context7 source in a run report.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Resolve-library-id
Find the matching library identifier for a package or product name.
Why this helps
Teams can lose track of which library documentation they used when integration work resumes months later.
- Make the documentation source easy to recover when work resumes.
- Surface ambiguous package names for review.
- Keep library identification separate from account data and affiliate reporting.
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 in plain language from any channel.
- 3In one instruction, ask Notis to resolve the Adtraction API or SDK package name you provide and report the compatible library ID and available versions.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with the package name from an integration you maintain.
Questions about this workflow
Does the workflow confirm which version my code uses?
It can report versions available in the Context7 result, but it cannot inspect your repository unless you provide that information in the request.
How often should I schedule it?
Choose a cadence that matches how often your team revisits the integration. The workflow performs a lookup; it does not monitor source code changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adtraction to Context7 MCP. A trigger fires from one place; an action lands in another.
Adtraction triggers
Context7 MCP actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query-docs
Retrieve current documentation and code examples for a programming library or framework.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Resolve-library-id
Find the matching library identifier for a package or product name.
Connect any two apps with Notis in the middle.
Adtraction 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.