Never lose specs when asking for clarification
Issue marked 'Needs Clarification'? Notis scrapes the linked spec so the asker has context ready.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Scrape HTML Elements
Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.
Why this helps
Founders mark issues for clarification but don't attach specs. The person clarifying has to hunt for context. Follow-up questions repeat. Time gets wasted.
- Specs are always available alongside clarification requests
- Reduce back-and-forth by giving clarifiers full context upfront
- Build a record of requirement changes over time
Setup
Build it in a few focused steps.
- 1Connect Linear and Cloudflare to Notis.
- 2Create an automation: 'When a Linear issue is updated and labeled with Needs Clarification, find the spec URL and scrape it.'
- 3Select 'Issue Updated' as the trigger.
- 4Choose your notification channel.
- 5Test by marking an issue as Needs Clarification with a spec URL.
Questions about this workflow
How do I specify which spec to scrape?
Include the spec URL in the issue description. When you apply the Needs Clarification label, Notis finds it and scrapes it.
Does this work for Figma links or Google Docs?
Yes, if Cloudflare can access them (most public/shared links work). Gated docs may not be fully accessible.
What if there are multiple spec links?
By default it scrapes the first. Refine your prompt to specify 'all URLs' if you need comprehensive coverage.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Cloudflare browser rendering. A trigger fires from one place; an action lands in another.
Linear triggers
Cloudflare browser rendering actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Capture Screenshot
Tool to capture a webpage screenshot. Use when you need a visual snapshot of a URL or HTML with optional viewport and clipping.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Accounts
Tool to list all Cloudflare accounts accessible. Use to retrieve a valid account_id for further browser rendering actions.
Comment Received Trigger
Triggered when a comment is received.
Scrape HTML Elements
Tool to scrape HTML elements for text, HTML, attributes, and box metrics. Use when you need detailed data of matched selectors after rendering a page.
Issue Created Trigger
Triggered when a new issue is created.
Take Webpage Snapshot
Tool to capture rendered HTML and screenshot of a webpage. Use when you need both DOM content and an image in one request with custom loading and capture settings.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Cloudflare browser rendering, 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 Cloudflare browser rendering.