Add vehicle context to GitHub issues from a VIN
Give Notis a VIN and the issue your team is tracking. It checks vehicle specifications and adds labels that make the issue easier to find and triage.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 details are easy to leave buried in lookup results instead of making them visible on the tracked issue.
- Make vehicle specifications visible through issue labels.
- Keep a vehicle investigation easier to search in GitHub.
- Avoid manually decoding a VIN before triage.
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 it for VIN issue labeling.
- 3In one instruction, ask Notis to look up the VIN specifications and add only relevant labels to the referenced existing GitHub issue.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one VIN and a real GitHub issue reference.
Questions about this workflow
Which vehicle details will become labels?
Specify the details that matter to your team in the instruction. CarsXE provides VIN specifications, but your preferred label vocabulary is up to you.
Will Notis create labels?
The GitHub action can add labels to an issue, and the supplied event description says labels that do not exist are created.
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.