Route Byteforms bug reports with GitHub issue labels
Collect a bug report in Byteforms, then have Notis label the GitHub issue it identifies so the right work 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
Bug details arrive in a form, but someone still has to find the matching issue and label it by hand.
- Triage a reported bug without switching between the form and GitHub.
- Apply labels named in the submission to an existing issue.
- Keep the report tied to the issue number supplied in the form.
Setup
Build it in a few focused steps.
- 1Connect Byteforms and GitHub once in Notis.
- 2Create an automation and describe how a submitted bug report should update its referenced issue with the requested labels.
- 3Pick a Notis webhook trigger and choose where run reports go.
- 4Configure Byteforms to send the submission to the webhook, then test with one real report and issue.
Questions about this workflow
Does this create a new GitHub issue?
No. This action adds labels to an existing issue, so the submission must identify the repository and issue.
Can labels be created if they do not exist?
Yes. GitHub's add-labels action creates labels that are not already present in the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Byteforms to GitHub. A trigger fires from one place; an action lands in another.
Byteforms 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.
Byteforms 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.