Route call feedback to the right GitHub issue label
Send call feedback and its related issue details to Notis. It can apply the label that makes the next step 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
Call feedback can sit apart from the code issue it needs to inform, leaving founders to connect the dots by hand.
- Keep relevant call feedback visible beside its GitHub issue.
- Apply labels based on the feedback details included in the webhook.
- Reduce manual issue triage after customer calls.
Setup
Build it in a few focused steps.
- 1Connect CallOnTheGo and GitHub once in the Notis portal.
- 2Create an automation in the portal or from any Notis channel.
- 3In one instruction, describe how to use webhook call feedback to label its linked GitHub issue.
- 4Choose the Notis webhook trigger and select where run reports should go.
- 5Test with one real example that includes call feedback and its related issue.
Questions about this workflow
What starts this workflow?
A request to its Notis webhook starts it. Include the call feedback and enough GitHub issue details to identify the issue.
Does CallOnTheGo provide a trigger event for this workflow?
No. The workflow uses a Notis webhook, which starts when it receives an HTTP request.
Can it create a GitHub issue?
No. Its listed GitHub action adds labels to an existing issue. Include the issue details in the webhook request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link CallOnTheGo to GitHub. A trigger fires from one place; an action lands in another.
CallOnTheGo 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.
CallOnTheGo 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.