Know the Designer's Work Before You Review - Instant Storefront Context
The moment you are assigned a review in Linear, Notis pulls up the designer's Cults storefronts so you have full context.
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
You get assigned design reviews but do not know what the designer has published on Cults, so reviews feel disconnected and lack context.
- Review context loads automatically
- No time spent hunting for designer portfolios
- Better feedback because you know their style
- Faster reviews with full information upfront
Setup
Build it in a few focused steps.
- 1Connect Linear and Cults to Notis
- 2Create an automation named 'Review Context' or tell Notis: 'Show me storefronts when I get review assignments'
- 3Give Notis this instruction: 'When I am assigned a design review issue in Linear, query Cults for the designer's storefronts and post a summary to the issue'
- 4Select 'Issue Updated' as your trigger and set it to watch for assignments to your user
- 5Test by assigning a review issue to yourself and verify storefronts appear in a comment
Questions about this workflow
How does Notis know which designer to look up?
Tell Notis to extract the designer name from the issue assignee field or a custom field, and it will query Cults for their storefronts.
Can I see collections too?
Yes. Include 'also list their collections' in your instruction and Notis will post the full portfolio.
What if a designer has no Cults account?
Notis will let you know in the comment: 'No Cults storefronts found' so you can look elsewhere.
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.