Route Arize AX trace findings to a GitHub issue owner
Send a trace finding with its issue and owner context, then let Notis add the assignee in GitHub.
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
Trace findings can be understood quickly but still sit in an issue without a clear owner.
- Give a trace investigation a clear owner
- Cut down on manual handoffs
- Keep issue follow-up tied to the reported finding
Setup
Build it in a few focused steps.
- 1Connect Arize AX and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for trace follow-up.
- 3In one instruction, tell Notis to add the responsible GitHub user as an assignee on the issue named in the incoming Arize AX trace report.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real trace finding that includes a repository, issue number, and assignable GitHub username.
Questions about this workflow
Will this create a GitHub issue?
No. This workflow assigns users to an existing issue, so include its repository and issue number in the incoming report.
What if the user cannot be assigned?
GitHub may reject the assignment or ignore it if the authenticated user lacks push access. Check the run report and repository permissions.
Does Arize AX provide the trigger event?
No Arize AX trigger events are available in this package. A Notis webhook starts the automation when it receives the trace finding.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Arize AX to GitHub. A trigger fires from one place; an action lands in another.
Arize AX 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.
Arize AX 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.