Keep partner GitHub access aligned with Lemlist
A small recurring check prevents stale access and awkward manual audits.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user is a repository collaborator
Checks if a user is a collaborator on a specified github repository, returning a 204 status if they are, or a 404 status if they are not or if the repository/user does not exist.
Why this helps
Partner access gets granted during a busy launch and is later forgotten, creating security and coordination gaps.
- Catches access mismatches on a predictable cadence
- Reduces manual spreadsheet checks
- Supports cleaner partner offboarding
Setup
Build it in a few focused steps.
- 1Connect Lemlist and GitHub to Notis once through the portal.
- 2Create a scheduled automation in Automations -> New Automation or ask Notis to create it.
- 3Instruct Notis: Check active Lemlist partner contacts against their expected GitHub collaborator status and report any mismatch.
- 4Choose notis_cron, set the review cadence, and select a reporting channel.
- 5Run one test review with a real partner record.
Questions about this workflow
Does this remove access automatically?
No. This workflow checks collaborator status and reports exceptions so you can decide what to do.
How often should it run?
Weekly is a practical default for partner access, with a more frequent cadence during launches.
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
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Lemlist and GitHub. Any 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.