Make repository access changes visible
New collaborator access gets a simple context trail so important security and onboarding details are not forgotten.
Trigger
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.
Action
Get Current User
Retrieves the currently authenticated user's information from SAP SuccessFactors.
Why this helps
Access changes often happen quickly, but their ownership and follow-up may remain implicit.
- Improves access-change awareness
- Supports onboarding follow-up
- Reduces security administration gaps
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.
- 3Tell Notis: “When a new GitHub repository collaborator is added, get the current SAP SuccessFactors user and report the collaborator, repository, permission, and access-change context.”
- 4Select the collaborator-added trigger, choose the run-report channel, and test with one safe access change.
Questions about this workflow
Can the report include permission level?
Yes. The collaborator event includes assigned role and permission details.
Does it grant access?
No. GitHub remains responsible for the access change; this workflow reports it.
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.
Get Current User
Retrieves the currently authenticated user's information from SAP SuccessFactors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
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 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.