Keep prediction scopes aligned with project changes
When plans change who should be included, refresh the scope that defines the prediction population.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Force Update Scope
Tool to trigger a rerun for a scope resource. Use when you need to force rebuild a scope, causing it to reprocess and update its data.
Why this helps
Changing a cohort or outcome in the plan can leave the scope behind unless someone remembers to refresh it.
- Rebuilds a scope after a meaningful population change.
- Keeps prediction instructions aligned with current project intent.
- Reduces the effort of checking for stale scope definitions.
Setup
Build it in a few focused steps.
- 1Connect Linear and Faraday to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set it up conversationally.
- 3Describe which population or outcome updates should rerun the relevant Faraday scope.
- 4Select the Linear Issue Updated trigger and a channel for reports.
- 5Test with one real update to prediction scope requirements.
Questions about this workflow
What will the scope rebuild do?
It triggers a rerun for an existing scope, which can be used to refresh its resource state.
Can this apply to a project update?
Use an issue update that carries the scope change, or choose a project-specific trigger if the change is recorded on a project.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Faraday. A trigger fires from one place; an action lands in another.
Linear triggers
Faraday actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Cohort
Tool to archive a cohort in Faraday. Use when you need to stop updates to a cohort while keeping it visible.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Connection
Tool to archive a connection in Faraday. Use when you need to stop updates to a connection while keeping it visible.
Comment Received Trigger
Triggered when a comment is received.
Archive Dataset
Tool to archive a dataset in Faraday. Use when you need to archive a dataset and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
Issue Created Trigger
Triggered when a new issue is created.
Archive Outcome
Tool to archive an outcome in Faraday. Use when you need to stop updates to an outcome while keeping it visible.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Archive Persona Set
Tool to archive a persona set in Faraday. Use when you need to stop updates to a persona set while keeping it visible.
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).
Archive Place
Tool to archive a place in Faraday. Use when you need to stop updates to a geospatial area or address set while keeping it visible.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Archive Scope
Tool to archive a scope in Faraday. Use when you need to stop updates to a scope while keeping it visible.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Archive Stream
Tool to archive a stream in Faraday. Use when you need to archive a stream and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
Connect any two apps with Notis in the middle.
Linear and Faraday, 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 Faraday.