Route recall review issues to the right owner
When a recall review comes in, Notis can check the VIN and assign the existing GitHub issue to the owner named in the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A recall review may be noticed without anyone being clearly responsible for moving it forward.
- Put a named owner on recall review work.
- Reduce the chance that a flagged issue sits unassigned.
- Keep the assignment attached to the existing GitHub issue.
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 clear name.
- 3Tell Notis to check the VIN for recall information and assign the referenced existing issue to the requested GitHub user when it qualifies for review.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with one real VIN, issue reference, and assignable GitHub user.
Questions about this workflow
Does this choose an owner automatically?
The webhook should include the GitHub username to assign, or your instruction must specify an ownership rule based on information you provide.
What if the GitHub user cannot be assigned?
GitHub may reject or ignore assignment when the user is not assignable or permissions are insufficient. Check the run report and repository access.
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.