Keep Keyword Opportunities Visible in GitHub
Set a review schedule and have Notis assess Ahrefs keyword data against the criteria in your instruction, then label the related issue you provide.
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
Keyword reviews are easy to postpone, and worthwhile opportunities can disappear in notes before anyone tracks them.
- Create a regular review point for keyword opportunities.
- Make a supplied GitHub issue easier to find when an opportunity qualifies.
- Reduce the effort of repeating the same review manually.
Setup
Build it in a few focused steps.
- 1Connect Ahrefs and GitHub once in the Notis portal.
- 2Create an automation under Automations, New Automation, with a name and prompt.
- 3Describe the keyword criteria and how Notis should label the existing GitHub issue you provide when a result qualifies.
- 4Choose a recurring schedule and a channel for run reports.
- 5Test once with real Ahrefs data and a supplied issue before relying on the schedule.
Questions about this workflow
Can the workflow find and create the matching GitHub issue?
No. The action adds labels to an existing issue. Your instruction or input must identify the issue.
Does a schedule provide historical keyword baselines?
Only use history or baselines that Ahrefs returns or that you provide. Include any comparison period or baseline Notis needs.
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.