Find API references after completed tasks
Turn a completed technical follow-up into a focused documentation lookup for the next step.
Trigger
Task Created or Completed
Triggers when a Task is created or when its status changes to Completed in Salesforce. Supports optional filtering by task Status or Subject.
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
Technical follow-up tasks often close without the API details needed to act on what was learned.
- Retrieve current API details tied to a completed task's stated question.
- Get code examples where Context7 has them.
- Make missing library names or API questions visible in the run report.
Setup
Build it in a few focused steps.
- 1Connect Salesforce and Context7 MCP once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name, prompt, report channel, and trigger.
- 3In one instruction, ask Notis to query current Context7 docs for the library and API question stated in the task context or instruction, and report any missing inputs.
- 4Pick Task Created or Completed as the trigger.
- 5Choose where run reports go, then test with one real completed task.
Questions about this workflow
Can I limit this to completed tasks?
The listed Task Created or Completed trigger supports optional filtering by task Status or Subject. Pick the trigger and use its available options as appropriate.
Does the workflow complete or modify tasks?
No. The available Context7 action retrieves documentation and code examples only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Salesforce to Context7 MCP. A trigger fires from one place; an action lands in another.
Salesforce 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.
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Contact Updated
Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
Connect any two apps with Notis in the middle.
Salesforce 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.