Hand off paid client onboarding in GitHub
Move from a confirmed payment to a clear owner for the next onboarding task.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
After payment, onboarding can stall while someone checks billing, finds the project task, and remembers to assign it.
- Give a paid onboarding task a named owner.
- Keep the handoff beside the work already being tracked.
- Cut the manual follow-up between billing and delivery.
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 assign the existing GitHub onboarding issue to the responsible teammate when a client payment is confirmed.
- 3Pick a webhook trigger so an incoming HTTP request starts the automation.
- 4Choose where Notis should send run reports.
- 5Test with one real payment and confirm the correct issue and assignee.
Questions about this workflow
Does this create an onboarding issue?
No. The available GitHub action adds or removes assignees on an existing issue. The prompt or webhook must identify the issue and teammate.
What happens if the teammate cannot be assigned?
GitHub may ignore changes if the authenticated user lacks push access. Check repository access and assignee eligibility when testing.
Can Altoviz start this automation directly?
Altoviz has no listed native trigger. A Notis webhook starts it when it receives an HTTP request containing the payment 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.