Skip to content
Notis

Make important issue movement visible

A change in state, owner, or milestone can alter your week. Create a receiver when a monitored issue meaningfully changes.

Trigger

Issue State / Properties Changed

Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.

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

Progress updates are easy to miss when issue changes happen asynchronously.

  • Surfaces changes that alter priorities
  • Preserves previous values for context
  • Reduces repeated issue-page checks

Setup

Build it in a few focused steps.

  • 1Connect GitHub and Proxiedmail to Notis once through the portal.
  • 2Create Meaningful issue change receiver.
  • 3Use the instruction: When the monitored GitHub issue changes state, assignee, milestone, labels, title, or lock status, create a Proxiedmail webhook receiver summarizing the changed fields, previous values, current issue, and link.
  • 4Select the issue state or properties changed trigger and choose the reporting channel.
  • 5Make one safe test property change and verify the receiver.

Questions about this workflow

Can it focus on state changes only?

Yes. Ask Notis to ignore unrelated property changes.

Are previous values available?

Yes. The trigger includes previous values for changed properties.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get API Token

Tool to retrieve a permanent api token. use after obtaining a bearer token from the auth endpoint (post /api/v1/auth).

ActionInstant

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.

TriggerPolling

List proxy bindings

Tool to fetch a list of proxy bindings. use after authentication to list all proxy bindings associated with the user.

ActionInstant

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.

TriggerPolling

Update Proxy Binding

Tool to update an existing proxy binding. use after obtaining the binding id to modify its addresses or settings.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.