Keep search opportunities visible in GitHub
Let Autom surface search changes on a schedule and have GitHub issues marked for the work they need.
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
Useful search findings can get buried in research notes while the related GitHub issue stays hard to spot.
- Turn recurring web research into visible issue triage
- Reduce manual searching through open issues
- Use labels to make search-related work easier to scan
Setup
Build it in a few focused steps.
- 1Connect Autom and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe the outcome in one instruction: search for the chosen topic, summarize notable changes, find relevant GitHub issues, and add an existing or appropriate label when useful.
- 4Pick a recurring schedule as the trigger and choose where run reports should go.
- 5Test with one real search topic and issue before relying on the workflow.
Questions about this workflow
Does Autom start this workflow with an app event?
No. Autom has no trigger events in this setup, so choose a Notis schedule.
Will the automation open new issues?
This workflow uses the listed GitHub action to add labels to issues. It does not create issues.
Can Notis decide which labels to use?
It can use labels that fit the research and existing issue context. Provide your label conventions in the instruction if they are not clear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Autom to GitHub. A trigger fires from one place; an action lands in another.
Autom 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.
Autom 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.