Give Recurring Ahrefs Audit Follow-up an Owner
A scheduled review can turn supplied audit findings into clearer follow-up by assigning the existing GitHub issues and owners you identify.
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
Repeating audits create follow-up work, and findings without named owners are easy to leave behind.
- Add ownership to existing issues during a recurring review.
- Keep audit follow-up moving without repeating manual assignment steps.
- Surface failures or unassignable users in run reports.
Setup
Build it in a few focused steps.
- 1Connect Ahrefs and GitHub once in the Notis portal.
- 2In Automations, New Automation, create a named automation and prompt.
- 3In one instruction, tell Notis which supplied audit findings merit follow-up and which provided GitHub issue and username to assign for each.
- 4Choose a recurring schedule and where run reports should go.
- 5Test with one real finding, issue, and username that can be assigned.
Questions about this workflow
Can Notis infer the issue number and owner from Ahrefs?
Only if that information is present in data Notis can access or is supplied by you. Provide the issue and owner when Ahrefs does not return them.
What happens if the automation cannot assign someone?
GitHub may silently ignore assignment changes if the authenticated user lacks push access. Check repository access and the run report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ahrefs to GitHub. A trigger fires from one place; an action lands in another.
Ahrefs 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.
Ahrefs 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.