Customer context for GitHub product requests
Let customer data inform what reaches your backlog.
Trigger
Issue Added Event
Triggered when a new issue is added to the repository.
Action
List Customers
Tool to get a list of customers. use when you need paginated customer lists with optional filters.
Why this helps
Feature requests are easy to prioritize by volume of comments instead of customer reality.
- Adds customer perspective to triage
- Limits extra reporting work
Setup
Build it in a few focused steps.
- 1Connect GitHub and Loyverse once in Notis.
- 2Create a new automation.
- 3Ask Notis to retrieve relevant Loyverse customer context for new product-request issues.
- 4Select the issue-added trigger and reporting channel.
- 5Test with a real request.
Questions about this workflow
Can I keep customer reports private?
Yes. Choose a private channel for run reports.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Loyverse. A trigger fires from one place; an action lands in another.
GitHub triggers
Loyverse actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Supplier
Tool to create a new supplier. use when you need to register a supplier in loyverse before purchases.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Category
Tool to delete a single category by id. use when you need to remove an unused or deprecated category.
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.
Delete Supplier
Tool to delete a specific supplier by id. use after confirming the supplier id to remove an existing supplier.
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 Category
Tool to get a single category by id. use when you need to fetch details of an existing category in loyverse.
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 Discount
Tool to get a single discount by id. use after confirming the discount id to retrieve its 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 Employee
Tool to get a single employee by id. use after confirming the employee id to fetch its details.
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 JWKS
Tool to fetch json web key set for openid connect. use when verifying loyverse id token signatures.
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 Merchant Info
Tool to get merchant information. use after authenticating to retrieve merchant account details.
Connect any two apps with Notis in the middle.
GitHub and Loyverse, 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 Loyverse.