Put the rollback runbook in reach when a deployment fails
Notis retrieves your canonical rollback Gist on a failed deployment and reports it in your chosen channel, cutting out the frantic document hunt.
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 Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
Why this helps
During a failed release, remembering where the current rollback commands live adds delay and avoidable stress.
- Surfaces the correct runbook immediately
- Shortens recovery time
- Avoids relying on memory during an incident
Setup
Build it in a few focused steps.
- 1Connect GitHub and Gist to Notis once.
- 2Open Automations in the portal and create Failed Deployment Rollback Runbook.
- 3Enter one instruction telling Notis to fetch the specified rollback Gist when the deployment state is failure or error and report the relevant steps.
- 4Choose New Deployment Status Created, select a report channel, and test with a safe failed deployment.
Questions about this workflow
Does Notis run the rollback automatically?
No. This automation retrieves and reports the runbook; it does not execute deployment commands.
Can I use a private Gist?
Yes, provided the connected Gist account can access it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Gist. A trigger fires from one place; an action lands in another.
GitHub triggers
Gist actions
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.
Check Gist Star
Tool to check if a gist is starred. Use when you need to determine if the authenticated user has starred a specific gist.
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.
Delete Gist Comment
Tool to delete a comment on a gist. Use when you have both the gist_id and comment_id and want to remove that comment. Example prompt: "Delete comment 42 from gist 'aa5a315d61ae9438b18d'".
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Gist
Tool to retrieve a specific gist by its ID. Use when you have a gist_id and need complete gist details.
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.
Get Gist Comment
Tool to get a specific comment on a gist. Use when you need to retrieve details of a particular comment given gist_id and comment_id.
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.
Get Gist Revision
Tool to retrieve a specific gist revision. Use when you need details of a past state for an existing gist by commit SHA.
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.
List Gist Comments
Tool to list comments on a gist. Use after confirming the gist_id to retrieve comments for a specific gist. Example: 'List comments for gist abc123'.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
List Gist Commits
Tool to list the commit history of a gist. Use after you have the gist ID to review its revisions.
Commit Event
Triggered when a new commit is pushed to a repository.
List Gist Forks
Tool to list forks of a gist. Use after obtaining a gist_id to retrieve all forks for the gist.
Connect any two apps with Notis in the middle.
Not just GitHub and Gist. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Gist.