Keep payment disputes visible in GitHub
A dispute should reach the people responsible for the related work without another manual handoff.
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
Disputes can sit unnoticed when billing alerts and project work live in separate tools.
- Put dispute follow-up in the team's existing GitHub queue.
- Reduce manual copying from billing notifications.
- Keep the dispute status visible alongside related work.
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 from any channel to flag the related GitHub issue when Altoviz reports a payment dispute.
- 3Pick a webhook trigger so an incoming HTTP request starts the automation.
- 4Choose where Notis should send run reports.
- 5Test with one real dispute and confirm the intended issue receives the label.
Questions about this workflow
Does Altoviz provide a native trigger for disputes?
No. Use a Notis webhook and have an HTTP request carrying the dispute details start the automation.
Will this create a GitHub issue?
No. The available action adds labels to an existing issue. The automation needs enough information in the webhook or your instruction to identify that issue.
Can Notis create a new label?
The GitHub action can add labels and creates labels that do not already exist, according to the supplied event details.
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.