Move data-source requests into Faraday dataset setup
Turn the request into a dataset setup step while its context is easy to find.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Create Dataset
Tool to create a new dataset in Faraday. Use when you need to define a new data source for analysis and predictions.
Why this helps
Data-source setup often requires a separate follow-up after the original issue has already moved out of view.
- Starts dataset setup from the issue that explains why it is needed.
- Keeps the data-source request and follow-through in a single workflow.
- Cuts down on repeated context gathering across tools.
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 tell Notis what to automate in plain language.
- 3Describe which new data-source issues should result in a Faraday dataset and how to name it.
- 4Select the Linear Issue Created trigger and a reporting channel.
- 5Test with one real issue for a data source.
Questions about this workflow
Can the instruction specify what the dataset is for?
Yes. Include the intended use and naming guidance in the plain-language instruction so Notis can use the issue context.
Do I need a separate automation for every dataset?
No. A single automation can handle matching new issues according to the instruction you give Notis.
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.