Review partner follow relationships
Keep outreach follow up visible without maintaining another spreadsheet.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a user follows another user
Checks if a github user `username` follows `target user`; returns a 204 http status if true, 404 if not or if users are invalid.
Why this helps
Relationship checks disappear when outreach work competes with delivery work.
- Keep outreach organized
- Spot missing follow ups
- Reduce manual checking
Setup
Build it in a few focused steps.
- 1Connect Check Cherry and GitHub once in Notis.
- 2Create an automation named Partner follow review.
- 3Tell Notis to check the specified GitHub follow relationships for active partner records.
- 4Choose a recurring schedule and a report channel.
- 5Test with one partner record.
Questions about this workflow
Can it check multiple partners?
Yes. Ask Notis to review all partner records returned for the selected outreach group.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Check Cherry to GitHub. A trigger fires from one place; an action lands in another.
Check Cherry 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.
Check Cherry 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.