Close the financial loop on secret remediation
The alert gets attention. The expense record should happen in the same flow.
Trigger
New Secret Scanning Alert Detected
Triggers when a new secret scanning alert is detected in a GitHub repository. Monitors open secret scanning alerts and fires an event for each newly detected alert. Supports filtering by secret type (e.g., personal access tokens, AWS keys) and by token validity status (active, inactive, unknown). The payload includes the alert number, secret type, validity status, resolution state, timestamps, URLs, and flags for push protection bypass, public exposure, and multi-repo detection.
Action
Create Expense
Tool to create a new splitwise expense. use when you need to record a payment or bill in a group or between users. provide either split equally or a custom users list for shares.
Why this helps
Rotating credentials and handling exposure can involve unexpected shared costs that are hard to remember later.
- Captures remediation spending alongside the alert
- Reduces forgotten emergency purchases
- Creates a clearer incident cost trail
Setup
Build it in a few focused steps.
- 1Connect GitHub and Splitwise to Notis once through the portal.
- 2Create an automation or ask Notis to create one in plain language.
- 3Tell Notis to create a Splitwise expense for a secret scanning alert when its remediation notes include a shared amount and payer.
- 4Select the secret scanning alert trigger, choose run-report delivery, and test with one real alert.
Questions about this workflow
Can the secret value be included?
No. The instruction should use alert metadata and remediation context without exposing secrets.
Can active secrets be treated differently?
Yes. Tell Notis to act only when the alert validity status or remediation notes meet your rule.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Splitwise. A trigger fires from one place; an action lands in another.
GitHub triggers
Splitwise 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.
Add Friend
Tool to add a new friend to splitwise. use when you have the friend's email and name details ready.
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.
Create Expense
Tool to create a new splitwise expense. use when you need to record a payment or bill in a group or between users. provide either split equally or a custom users list for shares.
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 Expense
Tool to delete an existing expense by its id. use after confirming you have a valid expense id.
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.
Delete Friend
Tool to delete an existing friend by id. use when you need to remove a friend relationship by its user id. call after confirming the correct friend id.
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.
Get Categories
Tool to retrieve expense categories. use when you need to list available categories before creating an expense.
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.
Get Currencies
Tool to retrieve a list of supported currencies. use when you need to display or validate currency options.
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.
Get Current User
Tool to retrieve information about the current authenticated user. use when you need profile details of the logged-in user.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Group Info
Action to retrieve information about a group.
Connect any two apps with Notis in the middle.
Not just GitHub and Splitwise. 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 Splitwise.