Skip to content
Notis

Resolve Context7 IDs for your IoT library list

Keep a clear list of Context7 library IDs for the packages and frameworks you choose to track in your device projects.

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

Looking up the correct Context7 ID each time you need documentation adds a small but persistent interruption.

  • Resolve multiple supplied package names in a single scheduled run.
  • Keep the library names and returned IDs together in a report.
  • Prepare IDs for follow-up documentation queries.

Setup

Build it in a few focused steps.

  • 1Connect Adafruit IO and Context7 MCP once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis which package or product names to resolve; include the list because no Adafruit IO dependency-list trigger is specified here.
  • 4Pick a recurring schedule as the trigger and choose where run reports should go.
  • 5Test with one real package name from your IoT project.

Questions about this workflow

Does resolving an ID check whether a library has new releases?

No. The resolve-library-id action finds Context7-compatible library IDs for names you provide.

Can I use the returned ID for a documentation query?

Yes. Use the returned ID with Context7's query-docs action, which requires a compatible library ID unless you already have one.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Adafruit IO to Context7 MCP. A trigger fires from one place; an action lands in another.

Adafruit IO triggers

Context7 MCP actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Query-docs

Retrieve current documentation and code examples for a programming library or framework.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Resolve-library-id

Find the matching library identifier for a package or product name.

ActionInstant

Connect any two apps with Notis in the middle.

Adafruit IO 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.