Close the loop on weekly technical research
A short weekly sweep turns scattered discoveries into a dependable reference list.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if repo starred by auth user
Use to determine if the authenticated user has starred a specific github repository, which is confirmed by an http 204 status (resulting in an empty dictionary in the response data); the action fails (e.g., http 404) if the repository is not starred or does not exist.
Why this helps
Interesting repositories collected during the week vanish into old campaign notes instead of becoming reusable resources.
- Closes the loop on research capture
- Creates a reusable technical shortlist
- Protects attention from scattered notes
Setup
Build it in a few focused steps.
- 1Connect Lemlist and GitHub to Notis once through the portal.
- 2Create a weekly automation in the portal or ask Notis to create it.
- 3Use this instruction: Every week, check whether repositories saved from Lemlist research are starred by the authenticated GitHub account and report any missing stars.
- 4Choose notis_cron, set the weekly schedule, and select a reporting channel.
- 5Test with the current week's research list.
Questions about this workflow
Can this run without a Lemlist integration event?
Yes. The weekly schedule is a Notis-native trigger.
What should the report include?
Ask Notis to include the repository name, URL, and star status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Lemlist to GitHub. A trigger fires from one place; an action lands in another.
Lemlist 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.
Lemlist 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.