Check a claim raised in an issue comment
Give a question in the thread a source trail before it becomes an assumption.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Search
Performs a web search for a query, scrapes content from the top search results using firecrawl, and returns details in specified formats.
Why this helps
Claims in busy threads can be accepted or forgotten without anyone checking the underlying evidence.
- Find public sources relevant to a specific claim.
- Support more grounded discussion in the issue thread.
- Reduce the chance of a research request getting lost.
Setup
Build it in a few focused steps.
- 1Connect Linear and Firecrawl to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3In one plain-language instruction, tell Notis to search for public sources when a comment asks to verify a claim and return links with a short evidence summary.
- 4Pick the Linear Comment Received trigger and a channel for run reports.
- 5Test with one comment that clearly states a claim to check.
Questions about this workflow
Does a search prove a claim is true?
No. Search results provide sources to inspect; a person should evaluate their reliability and context.
How should the comment phrase the request?
State the claim and what evidence would help verify it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Firecrawl. A trigger fires from one place; an action lands in another.
Linear triggers
Firecrawl actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel a crawl job
Cancels an active or queued web crawl job using its id; attempting to cancel completed, failed, or previously canceled jobs will not change their state.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Start a web crawl
Initiates a firecrawl web crawl from a given url, applying various filtering and content extraction rules, and polls until the job is complete; ensure the url is accessible and any regex patterns for paths are valid.
Comment Received Trigger
Triggered when a comment is received.
Extract structured data
Extracts structured data from web pages by initiating an extraction job and polling for completion; requires a natural language `prompt` or a json `schema` (one must be provided).
Issue Created Trigger
Triggered when a new issue is created.
Get the status of a crawl job
Retrieves the current status, progress, and details of a web crawl job, using the job id obtained when the crawl was initiated.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Map multiple URLs
Maps a website by discovering urls from a starting base url, with options to customize the crawl via search query, subdomain inclusion, sitemap handling, and result limits; search effectiveness is site-dependent.
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).
Scrape URL
Scrapes a publicly accessible url, optionally performing pre-scrape browser actions or extracting structured json using an llm, to retrieve content in specified formats.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Search
Performs a web search for a query, scrapes content from the top search results using firecrawl, and returns details in specified formats.
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 Firecrawl, 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 Firecrawl.