Give unpaid billing follow-up an owner
A scheduled review can turn an unresolved invoice into a clear next step in your existing GitHub queue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Unpaid items can linger when nobody owns the next follow-up or has time to reconcile two tools.
- Assign a clear owner to existing follow-up work.
- Catch unpaid invoices during a recurring review.
- Keep billing follow-up in the team's GitHub workflow.
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 unpaid invoices and assign each matching existing GitHub follow-up issue to its responsible teammate.
- 3Pick a recurring schedule as the trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real unpaid invoice and verify the issue and assignee.
Questions about this workflow
Can this find unpaid invoices without a schedule?
This workflow uses a Notis recurring schedule because Altoviz has no listed trigger events.
Does it decide who owns each invoice?
Notis can use the responsibility information available in Altoviz or details you provide in the instruction. If no reliable owner is available, that information must be supplied.
Does it add a GitHub issue?
No. The selected action changes assignees on an existing issue; it does not create new issues.
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.