Surface overdue follow-ups before they disappear
A daily signal turns quiet overdue work into an obvious next step.
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
Small follow-ups sit across fundraising and product queues until someone remembers to check them.
- Create one daily review point
- Make overdue work easy to scan
- Lower memory load
Setup
Build it in a few focused steps.
- 1Connect Blackbaud and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it conversationally.
- 3Instruct Notis to add an overdue-follow-up label to GitHub issues related to overdue Blackbaud tasks.
- 4Pick a recurring daily trigger and choose the channel for run reports.
- 5Test with one known overdue follow-up.
Questions about this workflow
How does Notis identify related issues?
You explain the relationship in the automation prompt, and Notis interprets the records and GitHub context.
Can the label be reused?
Yes. GitHub labels are created if needed and applied to matching issues.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blackbaud to GitHub. A trigger fires from one place; an action lands in another.
Blackbaud 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 Blackbaud 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.