Turn Bitly incident context into GitHub issue labels
Capture the link context and make the related issue easier to spot with labels, without adding another manual triage step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Incident links and their tracking issues can drift apart, making it harder to see which work needs attention.
- Use a webhook request to start triage from a Bitly event.
- Add labels to a specified repository issue.
- Make incident-related work easier to find in GitHub.
Setup
Build it in a few focused steps.
- 1Connect Bitly and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Describe in one instruction which supplied repository issue should receive which labels based on the Bitly event.
- 4Choose the Notis webhook trigger and include the repository, issue number, and labels in the request.
- 5Choose a report channel and test with one real incident link and a suitable issue.
Questions about this workflow
Does this react to Bitly events natively?
No native Bitly trigger is listed. A Notis webhook starts the workflow when it receives an HTTP request containing the event and issue details.
What happens if a requested label does not exist?
The GitHub action can create labels that do not already exist when adding them to an issue.
Can it assign the issue to someone too?
This workflow uses the add-labels action only. It does not assign an issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitly to GitHub. A trigger fires from one place; an action lands in another.
Bitly 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.
Bitly 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.