Label GitHub Issues via External Webhooks
Your external tools should be able to categorize work in GitHub. Use Notis webhooks to add labels to issues from any system or process.
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
Only Hubspot and manual GitHub actions can label issues. External systems can't trigger labeling, limiting workflow flexibility.
- Any external system can label GitHub issues via webhook
- Issues stay organized based on external data and events
- No manual labeling across tools required
- Enables complex multi-system workflows
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Ask Notis: 'Create a webhook that adds the [label name] to issue [issue number] when called.'
- 3Set up a Notis Webhook trigger and get the webhook URL.
- 4Configure your external system to send a POST request with issue details to the webhook URL.
- 5Test by triggering the webhook and verifying the label is added in GitHub.
Questions about this workflow
How do I identify which issue to label?
Pass the issue number or URL in your webhook payload. Notis can match issues by number, title, or custom identifiers.
Can I add multiple labels at once?
Yes, pass an array of label names in your webhook payload.
What if the issue doesn't exist?
Notis logs an error. You can configure it to create the issue or skip silently, depending on your preference.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Hubspot to GitHub. A trigger fires from one place; an action lands in another.
Hubspot triggers
GitHub actions
Contact Created Trigger
Contact Created Trigger
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Deal Stage UpdatedTrigger
Deal Stage UpdatedTrigger
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.
Not just Hubspot and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.