Check whether the gist is already saved
Add a quick GitHub gist status check to a Browserless research flow so useful references are easier to revisit.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Research references are easy to lose when you cannot tell whether you already saved them.
- Check whether a research gist is already starred.
- Use the gist ID surfaced by your browser process.
- Keep the status result with the research run.
Setup
Build it in a few focused steps.
- 1Connect Browserless and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe: Check whether the authenticated GitHub user has starred the gist identified by my Browserless research request and report the result.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real gist ID.
Questions about this workflow
Does this star the gist if it is not starred?
No. The action checks status only.
What does not found indicate?
The gist may not be starred or may not exist. Confirm the gist ID in the request context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Browserless to GitHub. A trigger fires from one place; an action lands in another.
Browserless 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.
Browserless 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.