Look up docs when a new Airtable view is created
Connect a new view event to a documentation question that your team wants answered at that moment.
Trigger
View Created
Triggers when a new view is created in an Airtable base.
Action
Query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
Why this helps
A new view can prompt follow-up implementation work, and the relevant docs are easy to lose in the shuffle.
- Start a docs query from an actual view creation event.
- Retrieve current docs and code examples for the specified library.
- Capture the question and library context in one automation prompt.
Setup
Build it in a few focused steps.
- 1Connect Airtable and Context7 MCP once in the portal.
- 2Create an automation and describe the docs question and compatible library ID to query when the view is created.
- 3Pick the View Created trigger.
- 4Choose where run reports go.
- 5Test with one real view creation and review the returned documentation.
Questions about this workflow
Will the new view name be treated as a library ID?
No. Supply a valid Context7-compatible library ID and the question in your prompt. The view event provides the trigger.
Can Context7 return code examples?
Yes. Query-docs retrieves up-to-date documentation and code examples for the specified library.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtable to Context7 MCP. A trigger fires from one place; an action lands in another.
Airtable triggers
Context7 MCP actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Resolve-library-id
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.
Base Metadata Changed
Triggers when an existing Airtable base changes its name or permission level.
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
User Profile Changed
Triggers when the connected Airtable user's profile information changes.
View Created
Triggers when a new view is created in an Airtable base.
View Deleted
Triggers when a previously known Airtable view is deleted.
View Metadata Changed
Triggers when an Airtable view changes its name or type.
Connect any two apps with Notis in the middle.
Airtable 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.