Keep website findings moving with GitHub issue owners
Have Notis review captured website findings on a schedule and assign related issues to the owners your team uses for that work.
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
Captured findings can remain unowned in GitHub, so nobody knows who should follow up.
- Surface unowned website follow-up issues
- Reduce the mental load of remembering who should take the next step
- Use your ownership rules in a plain language instruction
Setup
Build it in a few focused steps.
- 1Connect CaptureKit and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3Ask Notis to review recent CaptureKit findings, identify related GitHub issues, and assign them according to ownership guidance you provide.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real capture and a related issue.
Questions about this workflow
How does Notis know who to assign?
Include your team's ownership rules in the automation instruction. Notis can only apply guidance and information available to it.
Does CaptureKit provide a schedule trigger?
No. This workflow uses Notis's recurring schedule trigger to start the review.
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.