Review Cults download history alongside Jira updates
Bring relevant Cults download activity into the Jira issue context when work changes.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
It is easy to forget whether a model was already downloaded while coordinating related work across Jira and Cults.
- Check download history when an existing Jira issue changes.
- Summarize matching model activity for a quick status review.
- Reduce repeated searches for models that may already be in download history.
Setup
Build it in a few focused steps.
- 1Connect Jira and Cults once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3In one instruction, ask Notis to check Cults download history for activity relevant to each updated Jira issue and summarize matches.
- 4Pick the Jira Updated Issue trigger for the project you want to monitor.
- 5Choose a report channel, then test with one real issue update and relevant Cults history.
Questions about this workflow
Does this trigger on Jira comments?
No. The Updated Issue trigger does not fire on comment activity. It runs when an issue field changes in the configured project.
Can it prove that a particular team member downloaded a model?
Only if Cults returns that information in the available download history. Notis can report the returned data, but cannot infer missing history or attribution.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Cults. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira 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.