Make release freezes operational
A release status change can apply the access rule immediately.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add user access restrictions
Sets/replaces list of users allowed to push to a protected branch; usernames (e.g., `["user1"]`) must be a json array in request body (not schema parameters), an empty array `[]` removes all restrictions.
Why this helps
Release freezes depend on someone remembering a sensitive GitHub permission change at the right moment.
- Applies freeze rules consistently
- Reduces risky manual permission edits
- Keeps release state and repository access aligned
Setup
Build it in a few focused steps.
- 1Connect Fomo and GitHub to Notis once through the portal.
- 2Create a webhook automation or ask Notis to create it in plain language.
- 3Tell Notis: “When Fomo marks a release branch frozen, replace its allowed GitHub push users with the approved list.”
- 4Select the webhook and report channel, then test with one non-production branch.
Questions about this workflow
Can the allowed-user list be empty?
Yes. GitHub accepts an empty list to remove all user-specific push restrictions.
Should this be tested before production?
Yes. Start with a protected test branch and one real Fomo event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Fomo to GitHub. A trigger fires from one place; an action lands in another.
Fomo 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 Fomo 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.