Bring Cursor context to GitHub deployment status updates
Keep release troubleshooting connected to the agent work already underway.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
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.
Why this helps
A deployment status update can arrive long after investigation began, leaving important diagnostic context in another tool.
- Restores diagnostic history quickly
- Supports smoother incident handoffs
- Reduces repeated investigation work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cursor to Notis.
- 2Create a new automation in the portal.
- 3Tell Notis to retrieve the relevant Cursor agent conversation when the monitored deployment gets a new status.
- 4Choose the deployment-status trigger and a channel for reports.
- 5Create a test status update and confirm the context arrives.
Questions about this workflow
Which deployment does it watch?
Select the deployment you want to monitor when configuring the GitHub trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cursor. A trigger fires from one place; an action lands in another.
GitHub 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 Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
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.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
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.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub 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.