Turn vehicle recall lookups into GitHub issue triage
Send a VIN and issue reference to Notis. It checks available recall data and labels the existing GitHub issue so the next step is easier to spot.
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
Recall checks can get lost between vehicle research and the GitHub issue where your team tracks the work.
- See recall follow-up needs on the issue your team already uses.
- Reduce manual switching between vehicle data and GitHub.
- Use labels to make recall status easier to scan.
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 give it a name.
- 3Tell Notis to look up recalls for the VIN in each request and add relevant labels to the referenced existing GitHub issue.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one real VIN and GitHub issue reference.
Questions about this workflow
Does this create a GitHub issue?
No. The selected GitHub action adds labels to an existing issue, so include its repository and issue reference in the webhook request.
What if CarsXE returns no recall information?
Tell Notis how to handle an empty lookup in the automation instruction. It should not add a recall label without supporting data.
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.