Turn vendor page changes into labeled GitHub issues
When a monitored vendor page changes, have Notis review the Agenty result and label the GitHub issue you identify in your instruction.
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
Vendor updates can sit unnoticed when you have to compare pages, find the related issue, and classify it by hand.
- Bring monitored vendor changes into your existing issue triage
- Classify a known issue from the change details
- Reduce manual checking across browser and GitHub
Setup
Build it in a few focused steps.
- 1Connect Agenty and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation, and give it a name.
- 3Tell Notis to review the Agenty change details and add a relevant existing or new label to the GitHub issue and repository you specify.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one real page change and GitHub issue.
Questions about this workflow
Does this create a GitHub issue?
No. The selected GitHub action adds labels to an issue you identify in your instruction.
What starts the automation?
An HTTP request to the Notis webhook starts it. Configure your Agenty process to send the page change result to that webhook.
Can Notis decide which label to apply?
You can ask Notis to use the change details to choose a relevant label. Provide the repository and issue reference in your instruction or incoming data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agenty to GitHub. A trigger fires from one place; an action lands in another.
Agenty 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.
Agenty 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.