Call on call when GitHub reports a deployment failure
When a deployment status turns into a failure, put the signal in front of the person who can respond.
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
Make a phone call from agent
Initiate calls
Why this helps
A failed deployment can be easy to miss when status updates are buried among other work.
- Surface a failed deployment to the designated responder.
- Reduce the need to monitor deployment pages manually.
- Include relevant status context in the call when available.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bolna once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to call your on call contact through the selected Bolna agent when the deployment status indicates failure.
- 4Pick the GitHub New Deployment Status Created trigger for the deployment you want to monitor and choose a report channel.
- 5Test with one real deployment status and confirm the call and report are useful.
Questions about this workflow
Does this trigger monitor all deployments?
The event is for a specific deployment. Select the deployment to monitor when choosing the trigger.
Can Notis call for every status update?
Describe the failure condition in the instruction. The trigger fires for newly created deployment statuses, so the instruction should tell Notis which status merits a call.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bolna. A trigger fires from one place; an action lands in another.
GitHub triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
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.
Fetch all batches by agent id
List all batches for agent
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.
Get all agents
List all agents
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 all phone numbers
List all phone numbers for your 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.
Get execution by id
Retrieve specific execution by `execution 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.
Make a phone call from agent
Initiate calls
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.
Retrieve agent by id
Retrieve an agent
Connect any two apps with Notis in the middle.
GitHub and Bolna, 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 Bolna.