Control GitHub team project permissions from WhatsApp
A team needs access to a project. Instead of navigating GitHub's permission screens, you send a WhatsApp message specifying the team and access level, and Notis handles it.
Trigger
New Message Received
Triggered in real time when your WhatsApp Business number receives an inbound message from a customer (text, media, location, or contact). Delivered via the Cloud API webhook.
Action
Add or update team project permissions
Grants or updates a team's permissions ('read', 'write', or 'admin') for a specific project, which must exist within the specified organization and be linked to it.
Why this helps
GitHub permission menus are nested and hard to remember. Each permission change means context-switching and hunting for the right settings.
- Manage permissions without navigating nested GitHub menus
- Teams get access instantly when they need it
- Reduce permission request turnaround time
Setup
Build it in a few focused steps.
- 1Connect WhatsApp and GitHub to Notis.
- 2Create an automation: 'When I send a WhatsApp message with a team name, update their project permissions to read/write/admin'.
- 3Set the trigger to 'new message received'.
- 4Tell Notis which project and organization to target.
- 5Test by sending a message like 'Give backend team admin access to feature-planning project' and verify permissions update in GitHub.
Questions about this workflow
Can I set different permissions for different teams?
Yes. Specify the team and permission level in your WhatsApp message and Notis will apply it.
What if the team doesn't exist yet?
Notis will let you know the team isn't found. You can create it in GitHub first, then run the automation again.
Can I remove a team's access via WhatsApp?
You can set their permission to 'none' or 'pull only' to effectively limit access. For full removal, you'd need a separate automation or GitHub directly.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Whatsapp to GitHub. A trigger fires from one place; an action lands in another.
Whatsapp triggers
GitHub actions
Message Status Updated
Triggers when a WhatsApp message status changes. IMPORTANT LIMITATION: WhatsApp Cloud API does not provide a native polling endpoint for message status. Status updates are ONLY delivered via webhooks in real-time. This trigger cannot directly poll the WhatsApp API for status updates. This trigger will return empty results as WhatsApp does not support this operation. To track message status updates, you must: 1. Set up a webhook endpoint to receive status notifications from WhatsApp 2. Store the webhook data in your own database 3. Use a different mechanism to query your stored webhook data For more information, see: - https://developers.facebook.com/docs/whatsapp/cloud-api/webhooks
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
New Message Received
Triggered in real time when your WhatsApp Business number receives an inbound message from a customer (text, media, location, or contact). Delivered via the Cloud API webhook.
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.
Interactive Reply Received
Triggered when a customer taps a quick-reply button or selects an option from an interactive list message you sent.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Message Template Status Update
Triggered when the review status of a WhatsApp message template changes — for example approved, rejected, or flagged — on your WhatsApp Business Account.
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 Whatsapp 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.