Keep commission follow-up moving in GitHub
At your chosen cadence, have Notis review the Adtraction commission context you provide and assign the related GitHub issue to its owner.
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
Commission questions can linger when nobody is clearly responsible for the engineering follow-up.
- Put a named owner on existing commission related engineering work.
- Make recurring follow-up easier to remember.
- Keep the decision and run report in your chosen channel.
Setup
Build it in a few focused steps.
- 1Connect Adtraction and GitHub once in the Notis portal.
- 2Create an automation in the portal or from any channel.
- 3Tell Notis to review the commission follow-up information available to it and assign the linked existing GitHub issue to the named responsible person.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real commission review that includes a repository, issue number, and assignable GitHub username.
Questions about this workflow
Does Notis decide who owns a commission issue?
The instruction should identify the owner or provide a rule and the needed context. Notis can only assign an issue when it has a valid GitHub username and issue reference.
Will this assign every issue it finds?
Specify which linked issues qualify in your instruction. The GitHub action adds or removes assignees on a specified issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adtraction to GitHub. A trigger fires from one place; an action lands in another.
Adtraction 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.
Adtraction 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.