Keep Addresszen readiness visible as pull requests change
Every new commit can restart uncertainty. Keep one useful dependency check in the loop.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
Why this helps
Active pull requests change repeatedly, and manual rechecking after each update is easy to forget or postpone.
- Maintain readiness visibility through review iterations.
- Reduce repetitive manual checking.
- Help reviewers focus on code instead of coordination.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Addresszen to Notis once through the portal.
- 2Create an automation or ask Notis to check Addresszen key availability whenever a new commit is added to the selected pull request.
- 3Choose the pull request commit trigger and a report channel.
- 4Test with one follow-up commit on a real pull request.
Questions about this workflow
Can it watch one pull request?
Yes. Configure the specific pull request in the GitHub trigger.
Will every commit produce a report?
The trigger emits for new commits; describe any desired conditions in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Addresszen. A trigger fires from one place; an action lands in another.
GitHub triggers
Addresszen actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Key Availability
Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Resolve Address USA
Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.
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.
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 Addresszen, 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 Addresszen.