Turn Cloudsmith release signals into clear GitHub issue labels
When Cloudsmith sends a package release webhook, have Notis check its details and add relevant existing labels to the related GitHub issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Add labels to a repository issue.
Why this helps
Release follow-up gets lost when package details arrive separately from the GitHub issue tracking the work.
- Make release-related issues easier to scan.
- Keep package context close to the work being tracked.
- Reduce manual triage after a release event.
Setup
Build it in a few focused steps.
- 1Connect Cloudsmith and GitHub once in the Notis portal.
- 2Create an automation named for Cloudsmith release issue labeling.
- 3In one instruction, tell Notis to use the incoming package details to identify the related GitHub issue and add only relevant labels that already exist.
- 4Choose the Notis webhook trigger and configure Cloudsmith to send its release event to that webhook.
- 5Choose a run-report channel, then test with one real release payload that includes the related repository and issue reference.
Questions about this workflow
Does Cloudsmith provide a native Notis trigger for this workflow?
No. Start it with a Notis webhook and configure Cloudsmith to send an HTTP request when the relevant release event occurs.
What if the webhook does not identify a GitHub issue?
Have Notis report that it cannot identify a safe issue to update. Include a repository and issue reference in the incoming event or automation instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudsmith to GitHub. A trigger fires from one place; an action lands in another.
Cloudsmith triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accept a pending repository invitation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Abort Repository Migration
Aborts a queued or ongoing repository migration.
Add email for auth user
Add email addresses to your account.
Add app access restrictions
Allow apps to push to a protected branch.
Add a repository collaborator
Add a user as a repository collaborator or update their access.
Add field to user project
Adds a custom field to a user-owned project.
Add a repository to an app installation
Grant an app access to a repository.
Add item to user project
Adds an issue or pull request to a user-owned project.
Connect any two apps with Notis in the middle.
Cloudsmith 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.