Keep customer prediction outcomes current
Connect requirement changes to the outcome rebuild they call for, without relying on a separate reminder.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Force Update Outcome
Tool to trigger a rerun for an outcome resource. Use when you need to force rebuild an outcome, causing it to reprocess and update its predictions.
Why this helps
A changed prediction definition can leave prior outputs out of date while the rebuild waits in someone's mental queue.
- Starts a rerun when prediction requirements change.
- Keeps the model resource connected to its current definition.
- Removes a manual follow-up from the change process.
Setup
Build it in a few focused steps.
- 1Connect Linear and Faraday to Notis once.
- 2Create the automation through the portal or ask Notis in plain language.
- 3Describe what requirement changes should rerun the matching Faraday outcome.
- 4Choose the Linear Issue Updated trigger and a channel for run reports.
- 5Test using one real change to a prediction requirement.
Questions about this workflow
Does force update create a new outcome?
No. It reruns an existing outcome so it can reprocess and update its predictions.
Should every issue edit rebuild the outcome?
Specify which meaningful requirement changes should prompt a rerun so routine edits do not cause unnecessary work.
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.