Keep recurring campaign risks visible in GitHub
Let a scheduled Notis review make campaign risks easier to scan in the GitHub issues you use to track fixes.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Recurring campaign checks create follow-up work, but risk findings are easy to overlook in a separate review.
- Make recurring findings visible in the issue queue.
- Use labels to distinguish risk types that need attention.
- Reduce the effort of reviewing campaign checks and updating issues by hand.
Setup
Build it in a few focused steps.
- 1Connect Campaign Cleaner and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to review the available Campaign Cleaner results and add appropriate labels to the supplied existing GitHub issues; state how to handle missing issue details.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real review and a matching issue number.
Questions about this workflow
Can the scheduled review find GitHub issues by itself?
This package uses the available label action, which requires an issue number. Supply the issue details in the instruction or its input.
What if a scheduled review has no campaign results?
Have the instruction report that no findings were available and skip issue updates when the required campaign or issue details are missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Campaign cleaner to GitHub. A trigger fires from one place; an action lands in another.
Campaign cleaner 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.
Campaign cleaner 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.