Make reviewer relationships easier to revisit
Reviewer requests often mark who matters to a project. Preserve that signal without another item on your mental list.
Trigger
GitHub Pull Request Reviewers Changed
Triggers when the list of requested reviewers (users or teams) for a pull request changes — for example when a reviewer is added, removed, or re-requested. The payload includes the full current reviewer list (users and teams with details), which reviewers were added, which were removed, and the previous reviewer list for reference.
Action
Create Lead
Tool to add a new lead. use when you have lead details and need to save them to tomba.
Why this helps
Reviewer involvement is useful relationship data but rarely gets recorded outside GitHub.
- Preserve who is involved
- Improve collaboration follow-through
- Reduce scattered relationship notes
Setup
Build it in a few focused steps.
- 1Connect GitHub and Tomba to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create a Tomba lead for each newly requested reviewer and include the pull request context.
- 3Select the GitHub Pull Request Reviewers Changed trigger.
- 4Pick a channel for run reports and test with a reviewer request.
Questions about this workflow
Does it handle teams as well as individuals?
The GitHub event includes requested users and teams, so the instruction can account for both.
Can this be limited to important repositories?
Yes, monitor only the repositories where reviewer relationship tracking matters.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Tomba. A trigger fires from one place; an action lands in another.
GitHub triggers
Tomba 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.
List lead attributes
Tool to list all lead attributes. use when you need to discover available attributes before enrichment.
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.
Domain Status
Tool to check if a domain is webmail or disposable. use when validating email deliverability constraints.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete API Key by ID
Tool to delete an api key by id. use when you need to permanently revoke an api key before its expiration.
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 API Keys
Tool to list all api keys. use when you want to retrieve information about your existing tomba api keys.
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.
Create Lead
Tool to add a new lead. use when you have lead details and need to save them to tomba.
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.
List Leads
Tool to list all leads. use when you need to retrieve and paginate your leads list.
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.
Delete Leads List by ID
Tool to delete a leads list by id. use when you need to permanently remove a list after confirming its id.
Commit Event
Triggered when a new commit is pushed to a repository.
List Lead Lists
Tool to list all lead lists. use when you need to retrieve and paginate your lead lists.
Connect any two apps with Notis in the middle.
Not just GitHub and Tomba. 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 Tomba.