Keep release details from drifting unnoticed
Release notes, assets, and publication status stay visible as the release evolves.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Get Current User
Retrieves the currently authenticated user's information from SAP SuccessFactors.
Why this helps
Small release edits can create downstream work that is easy to forget or discover late.
- Surfaces release drift
- Supports reliable launch follow-up
- Reduces repeated release-page checks
Setup
Build it in a few focused steps.
- 1Connect GitHub and SAP SuccessFactors to Notis once.
- 2Create the automation or ask Notis to create it in plain language.
- 3Use the instruction: “When a monitored GitHub release changes, get the current SAP SuccessFactors user and report the changed fields, release, publication status, and assets.”
- 4Choose the release-state trigger, select the run-report channel, and test with one release update.
Questions about this workflow
Which release changes can trigger it?
The trigger covers title, notes, draft or prerelease status, publication time, target, and assets.
Can the report focus on published releases?
Yes. Ask Notis to emphasize the release state that matters to your process.
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.