Find the right library for your address integration
Start with the library name in your request. Notis resolves its Context7 ID so the next documentation lookup can target the right package.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Resolve-library-id
Find the matching library identifier for a package or product name.
Why this helps
A package name alone may not identify the exact library Context7 needs, which can derail a quick address integration task.
- Resolve a package name to a Context7-compatible library ID.
- Keep library identification attached to the address integration request.
- Prepare a valid identifier for a later documentation query.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Context7 MCP once in the Notis portal.
- 2Create an automation and name it for resolving address integration libraries.
- 3Tell Notis to read the library name and address workflow from each webhook request, then resolve the exact Context7-compatible library ID.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real request containing a library name and address integration context.
Questions about this workflow
Does this workflow query the library documentation too?
No. It resolves the library ID using the Context7 Resolve-library-id action. A separate query step would be needed to retrieve documentation.
What starts this workflow?
A custom backend or external tool sends an HTTP request to the Notis webhook with the library name and relevant address workflow context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Context7 MCP. A trigger fires from one place; an action lands in another.
Addresszen 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.
Addresszen 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.