Give every deployment status a reliable destination
Pending, successful, and failed deployments should not compete for your attention. Create a receiver automatically whenever GitHub publishes a status update.
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 webhook receiver
Tool to create a webhook receiver for incoming email callbacks. use when you need a unique endpoint to capture proxiedmail webhook events.
Why this helps
Deployment updates are easy to miss when releases happen across different environments and projects.
- Makes deployment transitions easier to track
- Separates release signals from general notifications
- Supports calmer environment monitoring
Setup
Build it in a few focused steps.
- 1Connect GitHub and Proxiedmail to Notis once through the portal.
- 2In Automations, create a workflow named Deployment status receiver.
- 3Describe the outcome in plain language: When GitHub creates a deployment status, create a Proxiedmail webhook receiver containing the repository, environment, state, commit, and deployment link.
- 4Choose the new deployment status created trigger and a reporting channel.
- 5Run one test deployment status and verify the receiver appears.
Questions about this workflow
Which deployment states are supported?
The trigger can respond to states such as pending, in progress, success, failure, error, inactive, and queued.
Can this cover production only?
Yes. State that the automation should act only on production deployment statuses.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Proxiedmail. A trigger fires from one place; an action lands in another.
GitHub triggers
Proxiedmail 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.
Create webhook receiver
Tool to create a webhook receiver for incoming email callbacks. use when you need a unique endpoint to capture proxiedmail webhook events.
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 API Token
Tool to retrieve a permanent api token. use after obtaining a bearer token from the auth endpoint (post /api/v1/auth).
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 proxy bindings
Tool to fetch a list of proxy bindings. use after authentication to list all proxy bindings associated with the user.
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.
Update Proxy Binding
Tool to update an existing proxy binding. use after obtaining the binding id to modify its addresses or settings.
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.
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Proxiedmail. 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 Proxiedmail.