Give recurring campaign fixes a clear GitHub owner
A scheduled review can surface open campaign work and put a supplied maintainer on the existing issue that tracks it.
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
Follow-up slips when recurring campaign findings have no clear owner in the team's GitHub queue.
- Make ownership part of a recurring campaign review.
- Keep the responsible maintainer visible on the existing fix issue.
- Lower the chance that follow-up depends on remembering a separate audit.
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 available campaign findings and add the supplied eligible maintainer to each specified existing GitHub issue that needs follow-up.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real review, issue number, and assignable username.
Questions about this workflow
Will this create issues for new findings?
No. The available action adds assignees to existing GitHub issues. Provide issue numbers for the findings you want tracked.
Can this assign anyone named in a finding?
Only if the username is assignable for that repository and the connected GitHub account has permission to make the change.
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.