Label GitHub issues from Ably release signals
Send a release signal through Ably and let Notis make the related GitHub issue easier to spot.
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
Release concerns shared in chat are easy to lose before anyone updates the issue.
- Keep release-related issues visible in the right queue.
- Reduce the manual step between a chat signal and issue triage.
- Let Notis interpret the incoming message before choosing a label.
Setup
Build it in a few focused steps.
- 1Connect Ably and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis to create one from any channel.
- 3In one instruction, ask Notis to read the incoming Ably signal and add an appropriate label to the GitHub issue identified in the request.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real Ably signal that identifies a GitHub issue.
Questions about this workflow
Does Ably provide the trigger for this workflow?
No. Use a Notis webhook as the trigger. An Ably subscriber or agent can send the signal to that webhook.
What should the request include?
Include enough context for Notis to identify the GitHub repository, issue, and release concern. Notis can choose or create an appropriate label based on the message.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to GitHub. A trigger fires from one place; an action lands in another.
Ably 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.
Ably 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.