Turn incoming requests into labeled GitHub issues
A clear request should arrive with a useful label. Let Notis interpret the webhook details and organize the matching 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
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
New issues pile up unlabeled, leaving you to reopen each one and decide what it needs.
- Make new issues easier to scan
- Reduce manual categorization
- Create labels when the issue needs one that does not exist
Setup
Build it in a few focused steps.
- 1Connect Apilio and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis how to interpret the incoming request and label the matching GitHub issue.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request and confirm the issue labels make sense.
Questions about this workflow
Does Apilio provide the trigger for this workflow?
Apilio has no listed trigger events here, so this workflow starts when an HTTP request reaches a Notis webhook.
Can the workflow use labels that are not in the repository yet?
Yes. The GitHub action creates labels that do not already exist when adding them to an issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apilio to GitHub. A trigger fires from one place; an action lands in another.
Apilio 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.
Apilio 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.