Triage Byteforms feedback against GitHub issues weekly
Set a regular review cadence for form feedback that references GitHub issues, and apply labels that help you decide what needs attention.
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
Feedback can accumulate in forms while related GitHub issues remain unlabeled and hard to prioritize.
- Review accumulated feedback on a predictable schedule.
- Add requested labels to the existing issues identified in submissions.
- Keep triage moving without checking forms manually each day.
Setup
Build it in a few focused steps.
- 1Connect Byteforms and GitHub once in Notis.
- 2Create an automation and describe how to review recent feedback submissions and label their referenced existing issues.
- 3Pick a Notis cron trigger, set its schedule, and choose where run reports go.
- 4Test with one real submission and issue, then keep the schedule that fits your review routine.
Questions about this workflow
Does this workflow search GitHub for a matching issue?
No. The submission needs to identify the existing GitHub repository and issue to update.
What if the feedback does not include labels?
Notis can only apply labels that the submission provides or that you explicitly describe as a rule in the automation prompt.
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.