Give call-related GitHub issues a clear owner
Turn a follow-up request into a visible owner on the GitHub issue it references.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
Follow-up work can stall when a call identifies an owner but the related issue remains unassigned.
- Make responsibility visible on the referenced issue.
- Reduce manual handoff after a follow-up call.
- Keep the follow-up tied to an existing 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 assign the referenced existing GitHub issue to the owner named in the Callingly follow-up request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with one real follow-up request that includes a repository, issue, and assignable GitHub username.
Questions about this workflow
What does the webhook need to include?
It needs to identify an existing GitHub issue and the intended GitHub username. GitHub may ignore assignment changes if the authenticated account lacks push access to the repository.
Can Notis make a new issue for the call?
No. This workflow uses GitHub's add-assignees action, which updates assignees on an existing issue.
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.