Add a reputation check to release changes
Release updates can trigger a quick signal about the addresses involved, without adding another launch-day task.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
Why this helps
Release communication often changes quickly, leaving little time to assess recipient risk manually.
- Supports safer launch outreach
- Reduces manual pre-announcement checks
- Keeps release changes actionable
Setup
Build it in a few focused steps.
- 1Connect GitHub and Abstract to Notis once through the portal.
- 2Ask Notis to score the reputation of email addresses associated with each changed GitHub release.
- 3Select GitHub Release State Changed as the trigger and choose where run reports should arrive.
- 4Test by updating a release note containing a representative email address.
Questions about this workflow
What release changes can trigger it?
The event covers changes to release title, notes, draft or prerelease state, publication details, target, and assets.
Can I use it for prereleases?
Yes. The trigger can monitor the release states relevant to your workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Abstract. A trigger fires from one place; an action lands in another.
GitHub triggers
Abstract actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
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.
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
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.
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 Abstract, 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 Abstract.