Skip to content
Notis

Check whether a repository is starred

Confirm a repository star from the Ably conversation where someone asked.

Trigger

Webhook received

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

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

Simple repository checks interrupt focused work when they require a manual GitHub lookup.

  • Answer a narrow repository question without a manual lookup.
  • Use the authenticated GitHub account's star status.
  • Return the check result through the run report.

Setup

Build it in a few focused steps.

  • 1Connect Ably and GitHub once in the Notis portal.
  • 2Create an automation in the portal or tell Notis to create one from any channel.
  • 3In one instruction, ask Notis to check whether the authenticated GitHub user has starred the repository identified in the incoming request.
  • 4Choose the webhook trigger and where run reports should go.
  • 5Test with one real repository request.

Questions about this workflow

Whose star status is checked?

The action checks the authenticated GitHub user's star status.

What should the request provide?

Identify the repository owner and repository name so Notis can check the intended repository.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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