Bring Ascora service context into GitHub issue labels
Send a service update with its linked engineering issue and labels so the issue is easier to scan in GitHub.
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
Useful service context can get lost when someone has to interpret an operations update and then label its engineering issue manually.
- Make relevant service issues easier to scan in GitHub.
- Use the labels and issue reference supplied in the Ascora request.
- Reduce repetitive triage steps after service updates.
Setup
Build it in a few focused steps.
- 1Connect Ascora and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to add the supplied labels to the linked GitHub issue named in an Ascora webhook request.
- 4Choose the notis_webhook trigger and where run reports should go.
- 5Test with one real request containing a repository, issue number, and labels.
Questions about this workflow
Can the automation create a label that does not exist?
Yes. The GitHub action adds labels to an issue, and labels that do not already exist are created.
Where do the labels come from?
Include the desired labels in the webhook request or specify a rule in your instruction. Ascora trigger data is not available unless sent to Notis.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ascora to GitHub. A trigger fires from one place; an action lands in another.
Ascora 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.
Ascora 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.