Keep reviewer relationships from getting lost
Every thoughtful review can become a relationship. Capture the context automatically.
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
Batch Enrich Contacts
Tool to batch enrich contacts with email validation and company info. use after gathering up to 250 contacts.
Why this helps
Reviewers provide valuable expertise, but their contact details are scattered across GitHub profiles and memory.
- Preserves context after a review conversation ends.
- Supports thoughtful follow-up with relevant people.
- Keeps relationship capture inside the existing engineering flow.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dropcontact to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to batch enrich each new pull request reviewer and report verified contact details.
- 3Pick the Pull Request Review Submitted trigger and select a run-report channel.
- 4Test it with one submitted review.
Questions about this workflow
Does it process every review type?
The trigger can cover submitted reviews; your instruction can focus the enrichment on approvals, comments, or requested changes.
Can I review results later?
Yes. Ask Notis to report results in your chosen channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dropcontact. A trigger fires from one place; an action lands in another.
GitHub triggers
Dropcontact actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Batch Enrich Contacts
Tool to batch enrich contacts with email validation and company info. use after gathering up to 250 contacts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Webhook Subscriptions
Tool to list webhook subscriptions. use when you need to inspect your configured webhooks.
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.
Retrieve Enrichment Results
Tool to retrieve enrichment results. use after submitting enrichment requests and use when you need to fetch the completed enrichment data by request 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.
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 Dropcontact, 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 Dropcontact.