Find the right docs for your Adtraction integration
Send Notis the Adtraction API or SDK name you are evaluating. It asks Context7 to find a compatible documentation source and returns the match for your next implementation step.
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
Starting from a vague package name can send you into the wrong docs and waste time on integration research.
- Identify a Context7-compatible documentation source before implementation.
- Keep API research in the same workflow as the integration request.
- Get a clear result when a product name matches multiple libraries.
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 name supplied with the request and return the matching Context7 library ID and available version details.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real API or SDK name you plan to use.
Questions about this workflow
What should I include in the request?
Include the Adtraction API, SDK, or package name you want to investigate. If you already know a preferred version, include it too.
Does this workflow call Adtraction?
No. It resolves a documentation source through Context7. It does not read Adtraction account data or make affiliate platform 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.