Keep Storefronts Clean - Auto-Archive Deprecated Models
Mark a model as deprecated in Linear and Notis removes the old version from your Cults storefront automatically.
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 model versions clutter your Cults storefronts and confuse users, but you forget to clean them up manually.
- Storefronts stay clean without manual effort
- Old versions never confuse your audience
- Audit trail shows what was archived and when
- One label triggers cleanup across Cults
Setup
Build it in a few focused steps.
- 1Connect Linear and Cults integrations to Notis
- 2Create an automation named 'Archive Old Versions' or ask Notis: 'Archive models when they get marked deprecated'
- 3Give Notis this instruction: 'When a design issue is labeled deprecated, query Cults and archive that model version across all collections'
- 4Select 'Issue Updated' as your trigger and watch for the 'deprecated' label
- 5Test by marking an old model issue as deprecated and verify it disappears from Cults within a minute
Questions about this workflow
Does archiving delete the model?
No. Archiving hides it from storefronts but keeps it accessible in Cults history for audit purposes.
Can I undo an archive?
Yes. Remove the deprecated label from the Linear issue and Notis can unarchive the model.
What if a model exists in multiple collections?
Notis archives it from all collections at once, so you do not need to manually update each one.
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.