Refresh product results when requirements change
A changed requirement can trigger a new product search, keeping the follow-up aligned with the current issue.
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 Products
Tool to retrieve products from best buy. use when you need to fetch product listings with optional filters and sorting. example: 'get products for category abcat0101000 sorted by saleprice.dsc.'
Why this helps
Old product research can linger after the need, budget, or other issue details change.
- Revisit product research after a relevant issue update.
- Base the search on current issue details.
- Make requirement changes easier to follow up on.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Best Buy once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to refresh Best Buy results when a monitored issue's product requirements change and summarize the updated request.
- 4Pick the GitHub Issue State / Properties Changed trigger and choose where run reports should go.
- 5Test with one real issue update that changes a product requirement.
Questions about this workflow
Can it compare products against an earlier search?
Only when that earlier search is available in the automation context. Otherwise, it can return fresh listings and describe the current requirements.
Will a change unrelated to products run a search?
Ask Notis to search only when the changed issue details affect a stated product requirement.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bestbuy. A trigger fires from one place; an action lands in another.
GitHub triggers
Bestbuy actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Categories
Tool to retrieve best buy product categories. use when you need to list or filter categories in the catalog.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Category Details
Tool to retrieve detailed information about a best buy category by its id. use when you need enriched metadata about a specific 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.
Get Product Details by SKU
Tool to retrieve detailed information about a specific product by sku. use after obtaining a valid sku to fetch its attributes.
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 Products
Tool to retrieve products from best buy. use when you need to fetch product listings with optional filters and sorting. example: 'get products for category abcat0101000 sorted by saleprice.dsc.'
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 Review Details
Tool to retrieve detailed information for a specific review by id. use after confirming the review 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.
Get Product Reviews
Tool to retrieve product reviews. use when you need customer feedback with filters or sorting. use after obtaining product skus.
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 Store Details
Tool to retrieve detailed information about a specific best buy store. use when you have a valid store 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.
Get Best Buy Stores
Tool to retrieve a list of best buy stores. use when you need store listings with optional filters or geo-search after confirming your api key.
Connect any two apps with Notis in the middle.
GitHub and Bestbuy, 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 Bestbuy.