Keep customer requests out of the mental backlog
Customer context arrives with a useful GitHub label, ready for a calmer prioritization session.
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
Feature requests get scattered across support conversations and are difficult to revisit when planning product work.
- Preserve customer-driven context
- Make later review faster
- Reduce ad hoc note-taking
Setup
Build it in a few focused steps.
- 1Connect Booqable and GitHub to Notis once through the portal.
- 2Create the automation in Automations -> New Automation or ask Notis to create it.
- 3Use this instruction: When a Booqable customer request becomes a product or integration issue, add the appropriate customer-request label to the related GitHub issue and retain the request context.
- 4Pick an incoming webhook trigger, choose the report channel, and test with one real request.
Questions about this workflow
Can different request types receive different labels?
Yes. Describe the classification rule in the plain-language instruction.
Does this prioritize the issue?
It labels the issue; your existing GitHub review process can use that label for prioritization.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Booqable to GitHub. A trigger fires from one place; an action lands in another.
Booqable 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.
Booqable 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.