Keep security response operationally grounded
A security alert can change priorities fast. Let Notis surface relevant Plisio operations alongside it.
Trigger
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.
Action
Get Plisio Operations
Tool to retrieve a list of operations (deposits and withdrawals). use when you need to fetch deposit and withdrawal transactions with optional filters and pagination. example: getoperations(currency='btc', limit=50).
Why this helps
Security response can crowd out financial monitoring and leave another risk unchecked.
- Create one response brief for two risk areas.
- Keep payment operations visible during incidents.
- Reduce parallel investigation and context switching.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Plisio to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Use this instruction: When a new GitHub code scanning alert is created, retrieve recent Plisio operations and summarize any deposits or withdrawals that may need review.
- 4Select the code scanning alert trigger and choose the channel for reports.
- 5Test it with one real or test alert.
Questions about this workflow
Can alerts be limited by severity?
Yes. Use the available GitHub trigger filters for the severity you care about.
Does it resolve the security alert?
No. It only adds Plisio operational context to the report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Plisio. A trigger fires from one place; an action lands in another.
GitHub triggers
Plisio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Balance
Tool to retrieve all account balances. use after api credentials are configured.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get All Balances
Tool to retrieve balances for a specific cryptocurrency. requires psys cid (currency code).
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.
Get Fee Plans
Tool to retrieve available fee plans for a given cryptocurrency. specify a currency symbol like 'btc', 'eth' to get fee plan details.
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.
Get Plisio Operations
Tool to retrieve a list of operations (deposits and withdrawals). use when you need to fetch deposit and withdrawal transactions with optional filters and pagination. example: getoperations(currency='btc', limit=50).
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Plisio Transactions
Tool to retrieve a list of transactions and invoices. use after authenticating with your api key to fetch historical operations with optional filters and pagination. example: gettransactions(status='paid', limit=20).
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.
Get Plisio Withdrawals
Tool to retrieve a list of withdrawal operations. use when you need to fetch only withdrawal operations with optional filters and pagination. example: getwithdrawals(status='paid', limit=20).
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 Plisio, 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 Plisio.