Keep Cursor API key details visible during Jira follow-up
When ticket changes prompt a workflow review, include the connected Cursor API key's name, creation date, and owner email for an authentication check.
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 API Key Info
Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.
Why this helps
Authentication details are easy to forget until a workflow needs attention, and finding them can interrupt Jira follow-up.
- Review key metadata in a Jira-triggered run report
- Keep authentication checks visible during issue follow-up
- Avoid repeated manual navigation for basic key details
Setup
Build it in a few focused steps.
- 1Connect Jira and Cursor once in the Notis portal.
- 2Create an automation and instruct Notis to retrieve Cursor API key information and report the returned metadata after an issue update.
- 3Pick the Jira Updated Issue trigger for the project you want to monitor.
- 4Choose where run reports should go, then test with one real issue update.
Questions about this workflow
Does this workflow reveal the API key secret?
No. The action retrieves key information such as its name, creation date, and owner email.
Will it trigger when someone comments on an issue?
No. The Updated Issue event does not fire on comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Cursor. A trigger fires from one place; an action lands in another.
Jira triggers
Cursor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Agent Conversation
Tool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get API Key Info
Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.
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 Agents
Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.
New Project
Triggered when a new project is added in Jira
List Available Models
Tool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.
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.
List GitHub Repositories
Tool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.
Connect any two apps with Notis in the middle.
Jira and Cursor, 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 Cursor.