Keep model request updates connected to model details
When a Jira request changes, retrieve the details for its confirmed model id to keep the decision context close at hand.
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
Get Model
Tool to retrieve details of a specific model by its id. use after confirming the model id is valid.
Why this helps
Model request changes can prompt another round of manual lookup and create avoidable context switching.
- Retrieve information for a specified model id
- Keep an updated request and reference together
- Reduce repeated manual model lookups
Setup
Build it in a few focused steps.
- 1Connect Jira and Anthropic administrator once in the Notis portal.
- 2Create an automation that retrieves details for a supplied model id after confirming it is valid.
- 3Choose the Jira Updated Issue trigger for the project where model requests are tracked.
- 4Choose where Notis should send run reports.
- 5Test with one updated request containing a confirmed valid model id.
Questions about this workflow
Does Get Model find or select a model?
No. It retrieves details for a specific id. Use List models to see available options before selection.
What if the update does not include a model id?
There is no model id to retrieve. Include a valid id in the request context before using this lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Anthropic administrator. A trigger fires from one place; an action lands in another.
Jira triggers
Anthropic administrator actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Message
Tool to create a new message completion. use when you need to generate assistant text given a conversation history.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Model
Tool to retrieve details of a specific model by its id. use after confirming the model id is valid.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List models
Tool to list available models. use when you need to see which models are available before selection.
New Project
Triggered when a new project is added in Jira
Prompt Caching
Tool to cache and reuse prompt content to reduce costs and latency. use after you have static prompt portions you intend to reuse across calls.
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 Anthropic administrator, 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 Anthropic administrator.