Bring job follow-up issues into view on schedule
At a cadence you choose, review job follow-up context and make related GitHub issues easier to spot.
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
Follow-up work can slip when job context and engineering issues are reviewed in separate places.
- Create a regular review point for job-related follow-up.
- Highlight linked issues using status and follow-up context available in AccuLynx.
- Reduce the need to remember which issues need another look.
Setup
Build it in a few focused steps.
- 1Connect AccuLynx and GitHub once in the Notis portal.
- 2In Automations, create an automation and describe: review AccuLynx jobs for follow-up context and add a chosen label to each linked GitHub issue that needs attention.
- 3Pick a Notis schedule for the review.
- 4Choose where run reports should go.
- 5Test with one real job and verify its linked GitHub issue receives the intended label.
Questions about this workflow
What does the scheduled review use?
It uses job and follow-up context available through the connected AccuLynx access. Specify the follow-up rule in the automation instruction.
How does Notis know which GitHub issue to label?
Provide a reliable link or repository and issue number in the AccuLynx job context or the instruction. Notis cannot infer missing issue links.
Can I choose how often it runs?
Yes. Choose the schedule when setting the trigger in the Notis automation setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Acculynx to GitHub. A trigger fires from one place; an action lands in another.
Acculynx 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.
Acculynx 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.