Scale Team Access Without Repo-Hopping
When you say 'add Jane to the repo' in Slack, Notis handles it in GitHub. Onboarding stays in sync across both tools.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Action
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.
Why this helps
You discuss adding a new team member to a repository in Slack, but then have to switch to GitHub and manually add their collaborator access. Often it's forgotten until they ask why they can't see the code.
- Onboarding happens immediately—no manual steps in GitHub
- Your team gets access right away, not hours or days later
- Slack is your single source of truth for who's joining which projects
Setup
Build it in a few focused steps.
- 1Connect Slack and GitHub integrations to Notis.
- 2Create an automation: 'When someone mentions adding a team member to a GitHub repo in Slack, add them as a collaborator with push access.'
- 3Specify which Slack channels should trigger this (e.g., #onboarding, #engineering).
- 4Choose a Notis channel for confirmation logs.
- 5Test by discussing adding a real team member in Slack—Notis will add them to GitHub and confirm.
Questions about this workflow
Can I control the permission level (push vs pull vs admin)?
Yes. When setting up, tell Notis what access level new collaborators should get. You can also say 'push access unless they're an intern' to add conditions.
What if the GitHub username differs from their Slack name?
Notis looks them up by email or real name first. If ambiguous, it asks your team in the Notis channel before granting access.
Does this only work for repos I'm an admin of?
Yes—Notis can only add collaborators to repos where your connected GitHub account has admin rights.
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.