Turn partner directory changes into a clear issue owner
Airtop checks the partner page on your schedule and assigns the issue you named when the page shows the condition you described.
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
A partner change can create follow-up work, but ownership gets lost when updates are only noticed during manual checks.
- Catch relevant directory changes on a schedule
- Assign the chosen issue when your stated condition is met
- Reduce the manual handoff from partner update to follow-up
Setup
Build it in a few focused steps.
- 1Connect Airtop and GitHub once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3In one instruction, name the directory page, condition, GitHub repository and issue, and intended assignee.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real directory entry and confirm the named user can be assigned.
Questions about this workflow
Can the automation choose any GitHub user?
The GitHub action only works for a user who can be assigned to issues in that repository. Specify the intended user in your instruction.
Will it assign the issue on every run?
Tell Notis to assign only when the directory page shows the relevant change. Review reports and tune that condition if repeated assignments are possible.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtop to GitHub. A trigger fires from one place; an action lands in another.
Airtop 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.
Airtop 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.