Capture research blockers after tracked time changes
Turn time spent into a clearer view of what is slowing implementation.
Trigger
Task Time Tracked Updated
Triggers when a time-tracking interval is created, edited, or deleted on a task. Fires once per interval-change. Reads ClickUp's top-level `data.description` for the lifecycle action and `data.interval_id` for the correlation key — these are unique to time-tracking events and are present even on Deleted (where `history_items` is empty).
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
Teams see rising tracked time but lack a quick explanation for the technical friction.
- Spot likely documentation gaps
- Suggest focused troubleshooting references
- Make recurring friction visible
Setup
Build it in a few focused steps.
- 1Connect ClickUp and Context7 MCP once in Notis.
- 2Create the automation and describe how to identify research blockers from the task context.
- 3Tell Notis to query Context7 after each interval change and report likely causes, relevant docs, and a next action.
- 4Pick ClickUp Task Time Tracked Updated as the trigger.
- 5Choose where reports go and test with one tracked-time interval update.
Questions about this workflow
Does the workflow know why time was spent?
Only if the task or time event description provides that context; otherwise it reports likely research areas.
Will it run for each interval change?
Yes. The event fires once per interval change.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Clickup to Context7 MCP. A trigger fires from one place; an action lands in another.
Clickup 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.
Folder Created
Triggers when a new Folder is created.
Folder Deleted
Triggers when a Folder is deleted.
Folder Updated
Triggers when a Folder is updated (renamed, content edited, etc.).
List Created
Triggers when a new List is created.
List Deleted
Triggers when a List is deleted.
List Updated
Triggers when a List is updated (renamed, content edited, etc.).
Connect any two apps with Notis in the middle.
Clickup 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.