Make approved specs visible in GitHub issue triage
When a specification is approved, send the related issue and labels to Notis to keep the next step visible 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
Approved specifications can be easy to miss when their GitHub issues still look like routine backlog items.
- Make approved specification work easier to find in the issue list.
- Reduce manual labeling after document review.
- Use labels supplied with the approval request; GitHub creates labels that do not already exist.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and GitHub once in the Notis portal.
- 2In Automations, choose New Automation and give it a name.
- 3Tell Notis to add the labels included in an approved specification request to its specified GitHub issue.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real approved specification example to the webhook and review the run report.
Questions about this workflow
How does the automation know which issue to label?
The webhook request should identify the GitHub repository and issue number, along with the labels to add.
Do the labels need to exist already?
No. GitHub's action creates labels that do not already exist.
What starts the workflow?
A Notis webhook request starts it. Have the ActiveMerge approval process send a request with the related issue and labels.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to GitHub. A trigger fires from one place; an action lands in another.
ActiveMerge 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.
ActiveMerge 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.