Put a person on each failed generation
Turn a failure update into a clear next step on the GitHub issue already tracking the task.
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
Failure alerts are easy to notice and just as easy to leave without an owner.
- Give an existing failure issue a clear owner.
- Cut down on manual handoffs after a failed run.
- Keep task follow-up in GitHub.
Setup
Build it in a few focused steps.
- 1Connect BytePlus Ark and GitHub once in Notis.
- 2Create an automation in Notis from any channel or in Automations, New Automation.
- 3In one instruction, tell Notis to add the supplied teammate as an assignee when an incoming Ark task update reports failure; include the existing issue reference.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real failure update and a teammate who can be assigned.
Questions about this workflow
Does this workflow choose an owner automatically?
No. Supply the teammate to assign in the update or automation instruction.
What if the issue reference is missing?
Notis needs the repository and issue context to target an existing GitHub issue.
Will GitHub always apply the assignment?
GitHub may silently ignore assignment changes if the authenticated user lacks push access to the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BytePlus Ark to GitHub. A trigger fires from one place; an action lands in another.
BytePlus Ark 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.
BytePlus Ark 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.