Control Branch Access Through Your System
Your access control system approves a team for production pushes—Notis updates GitHub protected branch permissions instantly.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add team access restrictions
Overwrites the list of teams (and their child teams) granted push access to a protected branch; the list of team slugs must be provided in the http post request body.
Why this helps
A team needs production branch access, but granting it in GitHub requires manual steps and understanding the branch protection UI. Access decisions are made outside GitHub but have to be manually mirrored back.
- Access control decisions flow directly from your system to GitHub
- No manual steps to grant team access
- Protected branch permissions stay in sync with your org's decisions
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis.
- 2Create an automation: 'When an external system sends a webhook saying a team is approved for production access, add them to the protected branch permissions.'
- 3Configure your access control system to send webhooks to Notis (webhook URL provided).
- 4Specify which team and which branch should receive access.
- 5Test by sending a webhook while the automation is listening.
Questions about this workflow
What information should the webhook include?
At minimum, the team name. You can optionally include the branch name and permission level if those vary by request.
Can I revoke access the same way?
Yes. Your access system can send a 'revoke' webhook to remove the team from branch permissions.
Does this handle multiple teams?
Yes. One webhook from your system can grant access to multiple teams if you structure the payload that way.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to GitHub. A trigger fires from one place; an action lands in another.
Slack triggers
GitHub actions
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
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.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
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.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
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.
Reaction Removed Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_REMOVED` instead. Triggered when a reaction is removed from a message.
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.
New Bot Message Received Trigger
DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` with `is_bot_message=true` instead. Triggered when a new bot message is posted to a Slack channel.
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 Slack and GitHub. Any combination from 985+ 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.