Find the right documentation library from an AimTell campaign
Turn campaign copy into a clear starting point for technical research. Notis identifies the referenced library and returns its Context7-compatible ID.
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
Campaigns can mention tools and frameworks without giving the team a reliable path to current documentation.
- Identify the likely library or framework referenced in campaign content.
- Get a Context7-compatible library ID to use in a follow-up documentation query.
- Reduce manual searching when campaign content sparks a technical question.
Setup
Build it in a few focused steps.
- 1Connect AimTell and Context7 MCP once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for campaign documentation lookup.
- 3In one instruction, ask Notis to inspect the incoming campaign content and use Context7 resolve-library-id to find the best matching library ID, noting ambiguity.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real campaign example and check the resolved library ID.
Questions about this workflow
Does this workflow retrieve documentation?
No. It uses the resolve-library-id action to find a Context7-compatible library ID. Use a separate query-docs workflow or automation to retrieve documentation.
What if campaign content mentions several technologies?
Tell Notis in the instruction to resolve each distinct library mentioned and flag uncertain matches for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link AimTell to Context7 MCP. A trigger fires from one place; an action lands in another.
AimTell 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.
AimTell 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.