Keep Adtraction transaction follow-up visible in GitHub
Send a transaction alert to Notis and have its existing GitHub issue labeled for the right follow-up.
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
Affiliate tracking problems can get buried when transaction alerts and engineering work live in separate tools.
- Make transaction related engineering work easier to scan.
- Keep the alert connected to an existing GitHub issue.
- Reduce manual triage after an affiliate tracking incident.
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 use each alert's linked existing GitHub issue and add an appropriate label, creating the label if needed.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real alert that includes a repository, issue number, and the context needed to choose a label.
Questions about this workflow
Does this create a GitHub issue?
No. The available GitHub action adds labels to an existing issue. Include its repository and issue number in the webhook information or your instruction.
What if the alert does not explain which label to use?
Tell Notis the label rules in your instruction, or include the needed context with the alert. Notis should not guess missing details.
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.