Keep important maintainer relationships visible
Close small networking loops while the context is still attached to the research.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if person is followed by authenticated user
Checks if the authenticated github user follows a target github user; an http 204 status indicates the user is followed, while an http 404 status indicates the user is not followed or the target user does not exist.
Why this helps
Useful maintainer names are captured in notes but relationship follow-up gets lost among product work.
- Keeps relationship follow-up visible
- Reduces repeated profile searches
- Connects research to a clear next step
Setup
Build it in a few focused steps.
- 1Connect Docparser and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it conversationally.
- 3Use one instruction: when parsed research names a maintainer, check whether my GitHub account follows that person and report any missing follow.
- 4Choose the incoming webhook trigger, select the reporting channel, and test with one research note.
Questions about this workflow
Does it follow people automatically?
No. It checks status and reports missing follows for your review.
Is this useful for partnership research?
Yes. It can turn technical or ecosystem research into a small, visible relationship follow-up list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Docparser to GitHub. A trigger fires from one place; an action lands in another.
Docparser 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.
Docparser 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.