Make overdue returns impossible to miss
A clear GitHub label turns a quiet overdue return into a visible next action.
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
Late returns are easy to lose among normal bookings and routine operational noise.
- Surface time-sensitive recovery work
- Separate overdue items from routine tasks
- Lower the need for manual monitoring
Setup
Build it in a few focused steps.
- 1Connect Booqable and GitHub to Notis once through the portal.
- 2Create an automation in Automations -> New Automation or ask Notis to set it up.
- 3Give Notis this instruction: When Booqable reports an overdue return, add the overdue-return label to the related GitHub issue and include the due date in the issue context.
- 4Pick an incoming webhook trigger and a reporting channel, then test using one overdue return.
Questions about this workflow
Can this run only for overdue items?
Yes. The incoming webhook should be sent when the Booqable return crosses its due time.
Will the label be created if needed?
GitHub can create labels when they do not already exist, subject to repository permissions.
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
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 Booqable and GitHub. Any 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.