Approve fork workflows without leaving WhatsApp
External contributors submit pull requests from forks. Instead of getting pinged to GitHub and hunting for the approval button, you get a WhatsApp prompt. One tap approves the workflow.
Trigger
Interactive Reply Received
Triggered when a customer taps a quick-reply button or selects an option from an interactive list message you sent.
Action
Approve a workflow run for a fork pull request
Approves a workflow run from a forked repository's pull request; call this when such a run requires manual approval due to workflow configuration.
Why this helps
Every fork PR requires you to jump to GitHub, find the workflow, and approve it manually. This context-switch breaks your focus.
- Approve fork workflows without visiting GitHub
- One tap in WhatsApp instead of three clicks in GitHub
- Stay in your flow state while still unblocking contributors
Setup
Build it in a few focused steps.
- 1Connect WhatsApp and GitHub to Notis (one-time in the portal).
- 2Create an automation: 'When a fork workflow needs approval, send me a WhatsApp button to approve it'.
- 3Set the trigger to 'when a workflow run awaits approval' (via a Notis webhook or your CI notifier).
- 4Choose WhatsApp as your notification channel.
- 5Test by triggering a fork workflow that requires approval and confirm you receive an interactive button prompt in WhatsApp.
Questions about this workflow
What happens if I tap the button after the workflow times out?
GitHub will reject the approval if the workflow has already been cancelled or completed. Notis will show you the error in your notification channel so you know it didn't go through.
Can I approve multiple workflows at once?
Each workflow gets its own WhatsApp prompt so you can handle each one on its own timeline. This prevents accidental bulk approvals.
Will contributors know I approved from WhatsApp?
No—the approval appears in GitHub as normal. Contributors just see that their workflow was approved; they won't know it came from WhatsApp.
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.