Keep scheduled vehicle value reviews visible in GitHub
Have Notis revisit a supplied vehicle list on a schedule, compare available market values with your team's thresholds, and label the related existing issues for review.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Vehicle values can change while review issues remain untouched, leaving teams without a visible cue to revisit them.
- Bring scheduled value checks back to the issues your team tracks.
- Apply your own thresholds consistently across a supplied vehicle list.
- Make review-needed issues easier to spot.
Setup
Build it in a few focused steps.
- 1Connect CarsXE and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the scheduled review.
- 3In one instruction, provide the vehicle-to-issue list and market value thresholds, then ask Notis to add a review label when a threshold is met.
- 4Pick a notis_cron schedule and choose where run reports should go.
- 5Test with one real vehicle, its existing GitHub issue, and a threshold you supplied.
Questions about this workflow
Where do the vehicle list and thresholds come from?
Provide them in the automation instruction or the information available to the scheduled run. CarsXE supplies market value data, not your team's baseline or review thresholds.
Can this open a new issue when a value changes?
No. This workflow uses the available GitHub action to add labels to existing issues.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CarsXE to GitHub. A trigger fires from one place; an action lands in another.
CarsXE triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
CarsXE and GitHub, 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 GitHub.