Check accessible Cursor repositories as Jira projects are added
A new project often means checking what codebases your team can access. Have Notis retrieve Cursor's accessible repository list and report the results.
Trigger
New Project
Triggered when a new project is added in Jira
Action
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.
Why this helps
New project setup can leave repository access checks scattered across tools and easy to postpone.
- Put a repository inventory in the project setup report
- Quickly review repositories visible to the connected Cursor account
- Create a consistent follow-up point when a Jira project appears
Setup
Build it in a few focused steps.
- 1Connect Jira and Cursor once in the Notis portal.
- 2Create an automation and describe how Notis should report the accessible Cursor repository list when a Jira project is added.
- 3Pick the Jira New Project trigger.
- 4Choose where run reports should go, then test with one real project creation event.
Questions about this workflow
Does the repository list include every repository in our organization?
The action returns repositories accessible to the authenticated Cursor user, which may not include every organization repository.
Can this workflow grant repository access?
No. The listed action retrieves the accessible repository list; it does not change access permissions.
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.