Reuse shared agent instructions with prompt caching
When your stable instructions are ready, trigger a run to prepare them for reuse and reduce repeated prompt costs and latency.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Long, repeated instructions can add unnecessary cost and delay when the same content is sent again and again.
- Start caching when shared instructions are ready
- Reuse static prompt portions across calls
- Reduce repeated prompt cost and latency
Setup
Build it in a few focused steps.
- 1Connect Jira and Anthropic administrator once in the Notis portal.
- 2Create an automation whose prompt identifies the static instructions intended for reuse.
- 3Choose a Notis webhook as the trigger.
- 4Choose where Notis should send run reports.
- 5Test the webhook with the supplied static instructions and review the run result.
Questions about this workflow
What starts this automation?
An HTTP request to its Notis webhook starts the run.
Should changing content be cached as static prompt content?
Use Prompt Caching for static prompt portions intended for reuse across calls. Supply the stable content and refresh it when your instructions change.
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.