Make approved access decisions real while context is fresh
The decision made in planning reaches the repository before it becomes another open loop.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add or update team repository permissions
Sets or updates a team's permission level for a repository within an organization; the team must be a member of the organization.
Why this helps
Access decisions are documented in meeting notes but never applied consistently.
- Closes the gap between decision and execution
- Reduces repeated access requests
- Keeps team permissions aligned with planning
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 an approved Scheduleonce planning webhook specifies a team, repository, and permission level, update that GitHub team repository permission and report the result.
- 4Choose the incoming webhook trigger and a channel for run reports, then test with one approved change.
Questions about this workflow
Will it act on unapproved requests?
The instruction should require an explicit approval signal before changing access.
Can it lower permissions too?
Yes, if the approved instruction specifies the new permission level.
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
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.
Scheduleonce 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.