Keep Collections Clean - Auto-Remove Deprecated Models
Close a design issue in Linear and Notis automatically removes the model from Cults and marks it as archived.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Cults GraphQL POST
Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.
Why this helps
Old, dead, or deprecated models linger in your Cults collections because manual cleanup is tedious and gets skipped.
- Collections stay clean without manual work
- Deprecated models never confuse users
- Audit trail shows what was removed and when
- Automatic cleanup reduces decision fatigue
Setup
Build it in a few focused steps.
- 1Connect Linear and Cults integrations to Notis
- 2Create an automation named 'Model Cleanup' or ask Notis: 'Remove models when issues are archived'
- 3Give Notis this instruction: 'When a design issue is archived or closed, remove that model from all Cults collections and mark it as deprecated'
- 4Select 'Issue Updated' as your trigger and watch for status changes to 'archived' or 'done'
- 5Test by archiving a design issue and verify the model disappears from Cults within a minute
Questions about this workflow
Does removal delete the model permanently?
No. The model is archived in Cults and hidden from storefronts, but kept for audit purposes.
Can I undo a removal?
Yes. Reopen the issue in Linear and Notis can restore the model.
What if a model is in multiple collections?
Notis removes it from all collections at once, keeping everything consistent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Cults. A trigger fires from one place; an action lands in another.
Linear triggers
Cults actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Approved Origins
Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cults GraphQL POST
Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.
Comment Received Trigger
Triggered when a comment is received.
Share on Create (FR)
Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.
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 Cults, 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 Cults.