Skip to content
Notis

Notice the issue changes that matter

Status, assignment, and priority changes become visible without forcing you to recheck every issue manually.

Trigger

Issue State / Properties Changed

Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.

Action

Get Current User

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

Why this helps

Important issue updates can blend into background activity until they become urgent.

  • Highlights meaningful changes
  • Cuts repetitive checking
  • Creates a clear audit trail

Setup

Build it in a few focused steps.

  • 1Connect GitHub and SAP SuccessFactors to Notis once.
  • 2Create an automation or ask Notis to create one.
  • 3Use the instruction: “When a monitored GitHub issue property changes, get the current SAP SuccessFactors user and report the changed fields, issue, and previous values.”
  • 4Choose the issue-property-change trigger, select the reporting channel, and test with one update.

Questions about this workflow

Which issue fields can trigger it?

The trigger supports changes to state, title, body, assignees, labels, milestones, locks, and more.

Can Notis summarize the change?

Yes. Ask for a concise plain-language summary in the automation prompt.

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.