Skip to content
Notis

Know whether your GitHub networking step is already done

A small relationship check can prevent duplicate outreach and help you focus on the people who still need a thoughtful introduction.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

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

Founders often save a contact for later and forget whether they already connected with them on GitHub.

  • Prevents duplicate networking actions
  • Creates a cleaner outreach queue
  • Keeps relationship maintenance lightweight

Setup

Build it in a few focused steps.

  • 1Connect TikHub and GitHub to Notis once through the portal.
  • 2Create an automation in the portal or ask Notis to create it in plain language.
  • 3Use this instruction: Review selected TikHub contacts and check whether my authenticated GitHub account follows each relevant GitHub user.
  • 4Choose a weekly trigger and a reporting channel, then test with one real contact.

Questions about this workflow

Does it follow the person automatically?

No. It checks current status and reports who still needs attention.

Can I define which contacts matter?

Yes. Include your criteria in the plain-language instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link TikHub to GitHub. A trigger fires from one place; an action lands in another.

TikHub triggers

GitHub actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

TikHub 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.