Make recurring website findings visible in GitHub
Send a CaptureKit crawl result to Notis and mark related GitHub issues with labels that help your team spot repeat findings.
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
Repeated crawl findings are easy to overlook when they are mixed in with unrelated GitHub work.
- Make recurring crawl problems visible at a glance
- Keep repeat findings connected to existing GitHub work
- Avoid manually reviewing every issue label
Setup
Build it in a few focused steps.
- 1Connect CaptureKit and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and add a name and prompt.
- 3Tell Notis to inspect each submitted crawl result, identify repeat findings when the crawl data shows them, find related GitHub issues, and add appropriate labels.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real crawl result and a related issue.
Questions about this workflow
Can Notis tell whether a finding is recurring?
Only when the submitted crawl data includes enough history or repeat evidence. If it does not, provide the baseline or history in your instruction or input.
Will this label every issue in the repository?
No. Ask Notis to label only issues it can relate to findings in the submitted crawl result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CaptureKit to GitHub. A trigger fires from one place; an action lands in another.
CaptureKit 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.
CaptureKit 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.