Align Tracking with Project Priorities Automatically
When a Linear project priority changes or the project gets archived, old ASIN tracking automatically clears. Monitoring stays aligned with what matters, no manual intervention.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Action
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Why this helps
Projects get reprioritized or archived in Linear but ASIN monitoring continues unchanged, wasting quota and cognitive energy on tracking that no longer supports active work.
- Keep ASIN tracking focused on high-priority projects
- Automatically remove monitoring when projects are deprioritized
- Reduce API quota waste on low-priority tracking
- Maintain tight alignment between project scope and monitoring work
Setup
Build it in a few focused steps.
- 1Connect your Linear workspace and Asin data api to Notis via the portal.
- 2Ask Notis: 'When a Linear project status changes to archived or priority changes to low, clear all ASIN tracking requests associated with that project.'
- 3Notis confirms: trigger is Project Properties Updated, action is Clear Collection Requests.
- 4Choose your reporting channel (Slack, email) for cleanup summaries.
- 5Test by archiving a project or changing its priority and verify the old tracking is removed.
Questions about this workflow
How does Notis know which tracking to clear?
You tag tracking with project identifiers in your prompt: 'Clear tracking tagged with this project name when the project is archived.' Notis matches on tags and removes associated requests.
Can I get approval before clearing?
Yes. Modify your prompt: 'When a project priority changes to low, show me the tracking that would be cleared and ask for confirmation before deleting.' Notis pauses for your go-ahead.
What if a project priority is restored?
The automation only triggers when priority lowers or project is archived. If you restore priority, the tracking remains cleared. You can ask Notis to re-add tracking if needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Asin data api. A trigger fires from one place; an action lands in another.
Linear triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific collection.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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 Asin data api, 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 Asin data api.