Mark GitHub issues that need attention after a call
Send a call escalation into Notis and keep the related GitHub issue easy 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
Urgent call details can get lost when you have to switch apps and manually update the related issue.
- Make call-related issues easier to find during triage.
- Reduce app switching after an escalation.
- Keep the change attached to the referenced GitHub issue.
Setup
Build it in a few focused steps.
- 1Connect Callingly and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to add an escalation label to the existing GitHub issue referenced in an incoming Callingly escalation.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real escalation that includes a GitHub repository and issue reference.
Questions about this workflow
Does this create a GitHub issue?
No. The selected GitHub action adds labels to an existing issue, so the incoming escalation must include a valid repository and issue reference.
Does Callingly provide a native trigger event?
No Callingly trigger event is listed here. Start this automation with a Notis webhook and send it the relevant escalation details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to GitHub. A trigger fires from one place; an action lands in another.
Callingly 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.
Callingly 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.