Keep useful code gists easy to find later
For reference gists shared during project work, Notis can check whether your account has starred them and include the status in a scheduled report.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if a gist is starred
Checks if a gist, identified by `gist id`, is starred by the authenticated user, returning an empty response (204) if starred, or a 404 error if not starred or not found.
Why this helps
Small code references and examples are easy to lose when you do not save them for later.
- Check specific gists you want to keep track of.
- Find out whether your account has starred each gist.
- Gather reference checks into one recurring report.
Setup
Build it in a few focused steps.
- 1Connect BSC Designer and GitHub once in Notis.
- 2Create an automation in any channel or in Automations, New Automation.
- 3Provide the gist IDs to check and ask Notis to report whether each is starred by your authenticated user.
- 4Pick a recurring schedule and choose where run reports go.
- 5Test with one real gist ID.
Questions about this workflow
Can this check any GitHub gist?
Specify the gist IDs you want checked. The action checks whether a gist is starred by the authenticated user.
Does the check star a gist for me?
No. It checks the current star status and reports the result.
What does a missing gist response mean?
The action reports an error when a gist is not starred or not found, so review the gist ID and result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BSC Designer to GitHub. A trigger fires from one place; an action lands in another.
BSC Designer 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.
BSC Designer 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.