Put a security advisory issue in someone's hands
When Agenty detects an advisory page change, ask Notis to summarize it and assign the GitHub issue you specify to its owner.
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
Advisory changes can require quick follow-up, but the issue can remain unowned while someone verifies the page and routes the work.
- Bring advisory page changes into the follow-up process
- Assign a specified issue to a known repository owner
- Keep the advisory summary with the run report
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 each Agenty advisory change, summarize the relevant details, and assign the GitHub issue and owner you specify.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one real advisory update and issue.
Questions about this workflow
Does this monitor advisories by itself?
Agenty supplies the page change result. Configure the Agenty process to send that result to the Notis webhook.
Does the workflow open or update issue text?
No. The selected action assigns an existing issue. The summary can be included in the Notis run report.
What if no matching issue is supplied?
The instruction needs a repository and issue reference, either specified in the instruction or provided with the run context.
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.