Turn Knack priorities into visible GitHub labels
See what matters most without rebuilding your whole plan.
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
Priority decisions get buried when the coding team cannot see them in the issue tracker.
- Makes urgent work easy to spot.
- Reduces mental effort during planning.
- Keeps the backlog aligned with current priorities.
Setup
Build it in a few focused steps.
- 1Connect Knack and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use this instruction: Review Knack priority records and add the appropriate labels to their matching GitHub issues.
- 4Choose a recurring trigger, select a reporting channel, and test it against one known priority item.
Questions about this workflow
How often can the review run?
Choose a recurring schedule such as daily or weekly when creating the automation.
What happens to labels?
Notis interprets the instruction and asks GitHub to add the relevant issue labels.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Knack to GitHub. A trigger fires from one place; an action lands in another.
Knack triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Knack and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.