Keep Faraday cohorts aligned with changed criteria
When the definition changes, prompt a cohort rebuild so the analysis reflects the updated audience.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Force Update Cohort
Tool to trigger a rerun for a cohort. Use when you need to force rebuild a cohort's data.
Why this helps
A cohort can quietly go stale after a criteria change if rebuilding it depends on someone remembering a separate follow-up.
- Triggers a rebuild when the underlying audience request changes.
- Keeps cohort membership aligned with current criteria.
- Avoids a separate manual refresh reminder.
Setup
Build it in a few focused steps.
- 1Connect Linear and Faraday once in the portal.
- 2Create an automation in the portal or describe it to Notis conversationally.
- 3Tell Notis which issue updates mean the named Faraday cohort needs a rebuild.
- 4Select the Linear Issue Updated trigger and a reporting channel.
- 5Test with one real criteria change and confirm the intended cohort is refreshed.
Questions about this workflow
Does this create a new cohort?
No. The Force Update Cohort action triggers a rerun for an existing cohort.
How does Notis know which cohort to refresh?
Include unambiguous cohort identification guidance in the plain-language instruction and relevant issue context.
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.