Give Competitor Change Follow-up a GitHub Owner
Send Notis a competitor change and the issue tracking your response. It can assign that issue to the owner you specify when the change meets your criteria.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Competitor monitoring can produce observations without a clear person responsible for deciding what to do next.
- Give a selected competitor response a clear owner.
- Keep the observation tied to an existing GitHub task.
- Reduce manual triage after monitoring alerts.
Setup
Build it in a few focused steps.
- 1Connect Ahrefs and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and add a name and prompt.
- 3Describe which supplied competitor changes warrant follow-up and which provided issue and GitHub username Notis should assign.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real competitor change and an issue with an assignable username.
Questions about this workflow
Does this automatically create a response plan?
No. It assigns an existing GitHub issue. Provide the issue and owner, and describe the criteria for assigning it.
Can the workflow compare current and previous competitor data?
Yes, if Ahrefs returns both periods or you provide a baseline. Otherwise, Notis cannot infer a historical change.
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.