Keep release email routing aligned with deployment changes
If a deployment moves environments or changes its release reference, keep its proxy binding current without another manual cleanup task.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
Update Proxy Binding
Tool to update an existing proxy binding. use after obtaining the binding id to modify its addresses or settings.
Why this helps
Routing details become stale when deployment environments or references change after setup.
- Reduces stale routing configuration
- Keeps deployment communication aligned
- Prevents avoidable manual updates
Setup
Build it in a few focused steps.
- 1Connect GitHub and Proxiedmail to Notis once through the portal.
- 2Create an automation named Deployment binding update.
- 3Write: When a GitHub deployment changes its environment, ref, task, or description, update the matching Proxiedmail proxy binding to reflect the current deployment routing details.
- 4Choose the GitHub deployment state changed trigger and a channel for run reports.
- 5Test with a non-production deployment detail change and verify the binding update.
Questions about this workflow
Does this create a new binding?
No. It updates an existing matching proxy binding.
What if the binding cannot be identified?
Have Notis report the run for review rather than changing an unrelated binding.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 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 proxy bindings
Tool to fetch a list of proxy bindings. use after authentication to list all proxy bindings associated with the user.
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.
Update Proxy Binding
Tool to update an existing proxy binding. use after obtaining the binding id to modify its addresses or settings.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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 Proxiedmail, 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 Proxiedmail.