Skip to content
Notis

Keep review coordination lightweight

Reviewer changes become visible at the moment they matter, so PRs keep moving without extra checking.

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

Get Current User

Retrieves the currently authenticated user's information from SAP SuccessFactors.

Why this helps

Review requests change over time, creating hidden coordination work and avoidable delays.

  • Reduces coordination overhead
  • Highlights blocked reviews
  • Creates a simple review trail

Setup

Build it in a few focused steps.

  • 1Connect GitHub and SAP SuccessFactors to Notis once.
  • 2Create the automation in the portal or ask Notis conversationally.
  • 3Use the instruction: “When requested reviewers change on a GitHub pull request, get the current SAP SuccessFactors user and report added, removed, and current reviewers.”
  • 4Choose the reviewer-change trigger, select a run-report channel, and test with one reviewer update.

Questions about this workflow

Can teams and individuals be reported?

Yes. The trigger payload includes both user and team reviewers.

Does it request reviewers automatically?

No. It reports the change and current SAP SuccessFactors user.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link GitHub to Sap successfactors. A trigger fires from one place; an action lands in another.

GitHub triggers

Sap successfactors actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Current User

Retrieves the currently authenticated user's information from SAP SuccessFactors.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

TriggerPolling

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.

TriggerPolling

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Connect any two apps with Notis in the middle.

GitHub and Sap successfactors, 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 Sap successfactors.