Bring overdue invoice follow-up into GitHub
A scheduled check can surface invoices that need attention in the project queue where the work is tracked.
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
Overdue invoices are easy to miss when someone must remember to check billing and then update project tracking by hand.
- Review overdue billing on a regular schedule.
- Make the follow-up visible in an existing issue.
- Reduce the need to remember separate billing checks.
Setup
Build it in a few focused steps.
- 1Connect Altoviz and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis to find overdue invoices and label the existing GitHub issue your team uses to track each related follow-up.
- 3Pick a recurring schedule as the trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real overdue invoice and verify the related issue is labeled.
Questions about this workflow
Does this create invoice reminders in GitHub?
It adds labels to existing GitHub issues. It does not create issues or send invoice reminders to customers.
What if an invoice cannot be matched to an issue?
Tell Notis how to identify the related issue. If the available invoice details do not contain a reliable match, supply the matching information or treat it as missing.
Can the schedule trigger use an Altoviz event?
Altoviz has no listed trigger events, so this workflow uses Notis's recurring schedule trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Altoviz to GitHub. A trigger fires from one place; an action lands in another.
Altoviz 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.
Altoviz 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.