Verify campaign technical claims against current documentation
Give reviewers documentation evidence alongside technical campaign claims, so they can assess accuracy without starting research from scratch.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Query-docs
Retrieve current documentation and code examples for a programming library or framework.
Why this helps
Reviewers may need to verify product and integration claims quickly, but campaign copy rarely includes the documentation behind them.
- Gather current documentation relevant to supplied technical claims.
- Return source references alongside the evidence.
- Make human review faster by keeping claims and documentation findings together.
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 claim checks.
- 3In one instruction, ask Notis to query the supplied Context7 library ID for documentation relevant to the incoming claims and report evidence with source references.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real claim and library ID, then review the cited documentation.
Questions about this workflow
Does this approve campaign claims automatically?
No. It gathers documentation evidence for a person to review; it does not make a final approval decision.
What should the webhook request include?
Include the technical claims to check and a valid Context7-compatible library ID. Resolve a missing ID before querying docs.
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.