Confirm the follow-up owner before it gets lost
Make sure the person leaving the call can actually receive the work.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user can be assigned to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
A promised owner may lack repository access or issue assignment eligibility.
- Prevents invalid handoffs
- Surfaces access problems immediately
- Protects meeting commitments from silent failure
Setup
Build it in a few focused steps.
- 1Connect Scheduleonce and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Tell Notis: When a Scheduleonce webhook names a GitHub follow-up owner, check whether that person can be assigned to the issue and report any problem.
- 4Choose the incoming webhook trigger and a channel for run reports, then test with one real attendee.
Questions about this workflow
What happens if the person cannot be assigned?
Notis reports the failed check so you can choose another owner or fix repository access.
Is this an access change?
No. It only verifies assignability.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Scheduleonce to GitHub. A trigger fires from one place; an action lands in another.
Scheduleonce triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Scheduleonce and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.