Keep customer context in the review loop
A review can change what ships next. Pair it with the payment context that may affect priority.
Trigger
Pull Request Review Submitted
Triggers when a new review is submitted for a GitHub pull request. Emits an event for each newly submitted review on the monitored pull request, covering all review types: APPROVED, CHANGES_REQUESTED, COMMENTED, and DISMISSED.
Action
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).
Why this helps
Product and revenue signals are easy to lose while focusing on code feedback.
- Connect code review with commercial context.
- Spot revenue-sensitive work sooner.
- Reduce switching between engineering and payment tools.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Plisio to Notis once through the portal.
- 2Create the automation in Automations or ask Notis to create it conversationally.
- 3Use this instruction: When a GitHub pull request review is submitted, retrieve recent Plisio transactions and summarize any payment context relevant to the change.
- 4Select the pull request review trigger and choose a channel for reports.
- 5Test it with one real review.
Questions about this workflow
Does every review start the workflow?
The configured GitHub review trigger can monitor the pull request or scope you select.
Does it approve or modify the pull request?
No. It only retrieves payment history and reports the result.
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
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 Balance
Tool to retrieve all account balances. use after api credentials are configured.
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 All Balances
Tool to retrieve balances for a specific cryptocurrency. requires psys cid (currency code).
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 Fee Plans
Tool to retrieve available fee plans for a given cryptocurrency. specify a currency symbol like 'btc', 'eth' to get fee plan details.
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 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).
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 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).
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 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).
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.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Plisio. Any 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.