Keep moving pull requests connected to their people
Each new commit can preserve the human thread around the review, without another reminder to yourself.
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
Add Recipient to Group
Tool to add a recipient to a recipient group. use when you need to add new mailing list subscribers.
Why this helps
Repeated review cycles create small coordination tasks that are easy to lose between code changes.
- Keeps review contributors easy to find
- Supports repeated review cycles
- Reduces mental tracking across tools
Setup
Build it in a few focused steps.
- 1Connect GitHub and Stannp once in the portal.
- 2Create an automation or tell Notis to add the relevant pull request contributors to a Stannp review group when a new commit arrives.
- 3Choose the new commit added to pull request trigger and describe the repository or branch scope.
- 4Select a report channel and test with one real pull request commit.
Questions about this workflow
Why trigger on a new PR commit?
It marks a fresh review cycle and can reopen the communication context around the change.
Can I monitor one pull request?
Yes. Configure the GitHub trigger for the specific pull request when that level of focus is useful.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Stannp. A trigger fires from one place; an action lands in another.
GitHub triggers
Stannp actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Recipient to Group
Tool to add a recipient to a recipient group. use when you need to add new mailing list subscribers.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create recipient group
Tool to create a new recipient group in stannp. use when you need to organize contacts into a distinct group before sending campaigns.
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.
Get Contact
Tool to retrieve details of a specific contact. use when you need all stored fields of a contact by its id.
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.
Import Recipients
Tool to import recipients from a csv or xls file into a stannp recipient group. use when you have a mailing list file ready to upload.
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 Contacts
Tool to list all contacts. use when you need to retrieve contacts with optional pagination filters.
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.
List Templates
Tool to list all templates associated with the account. use when you need to retrieve available templates after authentication.
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 Stannp, 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 Stannp.