Make call follow-ups easier to find in GitHub
Set a recurring review so call follow-up context can be checked and linked GitHub issues labeled when they need attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Follow-up work from calls can fade from view when there is no regular moment to review the open loop.
- Create a recurring checkpoint for call-related follow-ups.
- Make issues needing attention easier to spot with labels.
- Reduce reliance on memory for periodic review.
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 which available call follow-up context should result in a label on its linked GitHub issue.
- 4Choose a recurring Notis schedule and select where run reports should go.
- 5Test with one real example of available call context and a linked GitHub issue.
Questions about this workflow
What starts this workflow?
A recurring Notis schedule starts it. Choose a cadence that fits your follow-up review routine.
What call data will it review?
The automation can use CallOnTheGo information available to it. Specify the relevant follow-up context in your instruction, and provide any missing issue links or decision criteria.
Does it create or close issues?
No. The listed GitHub action adds labels to an existing issue.
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.