Turn deployment failures into immediate human action
Production issues deserve a direct path to the person who can fix them.
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
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead details.
Why this helps
A failed deployment can create uncertainty while the founder checks GitHub, hosting, chat, and incident tools.
- Cuts dashboard monitoring
- Escalates failures immediately
- Includes deployment context for faster response
Setup
Build it in a few focused steps.
- 1Connect GitHub and Callingly to Notis once.
- 2Create the automation in the portal or ask Notis to create it.
- 3Tell Notis in one instruction to create a Callingly outbound call when a deployment status indicates failure or error, including the environment and deployment link.
- 4Pick the deployment-status-created trigger, choose the run-report channel, and test with a real failed status.
Questions about this workflow
Can production be handled differently from staging?
Yes. Mention the environments and escalation rules in the plain-language instruction.
Does this monitor deployment status changes?
It reacts when a new deployment status is created for the monitored deployment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Callingly. A trigger fires from one place; an action lands in another.
GitHub triggers
Callingly 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.
Activate/Deactivate Client Account
Tool to activate or deactivate a client account. use when you need to toggle client access after onboarding or offboarding. example: "activate client 123" or "deactivate client 456".
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.
Create Agent
Tool to create a new agent. use when you need to register an agent in callingly after gathering their account id and contact details.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Outbound Call
Tool to create a new outbound call record. use after gathering call and lead 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.
Create Client
Tool to create a new client. use when adding a new client to your callingly account.
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.
Create Team
Tool to create a new team. use when setting up a team configuration before adding agents.
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.
Create Webhook
Tool to create a new webhook for call or lead events. use when you need to receive real-time notifications on specific events. example: "create a webhook for call completed events to http://example.com/callback".
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.
Delete Agent
Tool to delete an agent. use when permanently removing an agent after confirming the agent id.
Commit Event
Triggered when a new commit is pushed to a repository.
Delete Client
Tool to delete a client. use when you need to remove an existing client from your account after confirming its id.
Connect any two apps with Notis in the middle.
Not just GitHub and Callingly. 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 Callingly.