Never lose the thread after a code review
Reviews create decisions; this workflow helps turn those decisions into visible next steps.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
Why this helps
Approvals and requested changes often require separate follow-up that gets lost between coding tasks.
- Makes review outcomes actionable
- Reduces manual chasing
- Keeps collaborators aligned
Setup
Build it in a few focused steps.
- 1Connect GitHub and Mailsoftly once through Notis.
- 2Create the automation in the portal or ask Notis to authenticate Mailsoftly and prepare different follow-up messages for approvals, requested changes, and comments.
- 3Choose Pull Request Review Submitted and select the run-report channel.
- 4Test it with one real submitted review.
Questions about this workflow
Can different review outcomes use different wording?
Yes. Describe the desired response for each review type in the prompt.
Will review comments be duplicated?
The workflow responds to submitted reviews; use a separate comment trigger only if you need every inline comment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Mailsoftly. A trigger fires from one place; an action lands in another.
GitHub triggers
Mailsoftly actions
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.
Authenticate Firm
Tool to validate the api key and retrieve firm details. use when confirming credentials before making other mailsoftly api calls.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Mailsoftly. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Mailsoftly.