Configure GitHub branch protection from WhatsApp
Your team wants to require additional status checks before merging to main. Send a WhatsApp message specifying the check name and Notis adds it to your branch protection rules.
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 status check contexts
Adds status check contexts (provided in the request body, e.g., `{"contexts": ["new-context"]}`) to a protected branch, requiring these contexts to have been previously reported.
Why this helps
Branch protection settings are buried in GitHub. Adding new status checks means hunting through pages of settings, and your team has to repeat the process for each repo.
- Enforce status checks without visiting GitHub settings
- New checks take effect immediately
- Standardize branch protection across repos without manual configuration
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 status check name, add it to my protected branch'.
- 3Set the trigger to 'new message received'.
- 4Specify which branch and repository to protect.
- 5Test by sending a message like 'Add 'security-scan' to status checks for main branch' and verify it appears in GitHub branch settings.
Questions about this workflow
Will this break existing workflows if the status check doesn't exist yet?
No. GitHub allows you to add a status check name before it's been reported by CI. It just won't pass until that check actually runs.
Can I add multiple status checks at once?
Yes—list them all in one WhatsApp message and Notis will add each one.
Can I remove a status check via WhatsApp too?
This workflow adds checks. For removal, you'd need to set up a separate automation or use 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 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.