Keep GitHub tracking in step with Ark
A scheduled status review helps your issue queue reflect what is happening with tracked video tasks.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Task status changes can be missed when nobody remembers to revisit the generation dashboard.
- Bring changed task statuses back into the team's GitHub queue.
- Reduce manual dashboard checks.
- Make task state changes easier to spot.
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, describe which tracked tasks to review and how to label their existing GitHub issues when Ark reports a status change; provide the issue references and desired label meanings.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real task whose current status and GitHub issue are known.
Questions about this workflow
Can this compare status against a previous run?
Only if the needed prior status or baseline is available to Notis. Supply a baseline if the connected task data does not provide one.
Does it create the tracking issue?
No. The available GitHub action adds labels to existing issues.
How often should it run?
Choose a cadence that fits how quickly your team needs to see task changes.
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.