Stay Organized - Auto-Create Collections on Project Launch
Each time you create a project in Linear, Notis spins up a matching Cults collection so your models are organized from day one.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
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
You launch new design projects but forget to create Cults collections, leaving models scattered across your account with no clear organization.
- Collections are ready before designs arrive
- Models stay organized by project automatically
- No setup bottleneck slowing down creative work
- Reduces scattered, hard-to-find models
Setup
Build it in a few focused steps.
- 1Connect Linear and Cults integrations to Notis
- 2Create a new automation called 'Collections for Projects' or ask Notis: 'Create Cults collections when I start projects'
- 3Give Notis this instruction: 'When a new project is created in Linear, create a matching collection in Cults using the project name and description'
- 4Select 'Project Created' as your trigger
- 5Test by creating a new project in Linear and verify the collection appears in Cults
Questions about this workflow
Can I customize the collection name?
Yes. Tell Notis to use a specific naming pattern, like 'Project - [name]' or just the project name without the team prefix.
What if I don't want collections for every project?
Add a filter to your instruction: 'only if the project has the label client-work' to skip internal or experimental projects.
Can Notis set collection privacy automatically?
Yes. Include privacy settings in your instruction: 'create as private' or 'public' based on your preference.
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.