Check priority pull requests for merge status
Know which decisions are complete without repeatedly opening GitHub to check.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
A founder approves a change, then has to remember to revisit the pull request later to confirm it shipped.
- Closes the loop on delegated work
- Reduces repeated checking
- Keeps launch dependencies visible
Setup
Build it in a few focused steps.
- 1Connect GitHub to Notis once through the portal; connect 2chat if you want WhatsApp reports.
- 2Create the automation in the portal or ask Notis to create it.
- 3Use this instruction: On each weekday check, verify whether the specified priority GitHub pull requests have merged and summarize any that are still open.
- 4Choose a recurring schedule and run-report channel, then test with one active pull request.
Questions about this workflow
Can it monitor several pull requests?
Yes. List the pull requests or describe the label, milestone, or repository scope Notis should use.
Does it merge the pull request?
No. It only checks and reports merge status.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 2chat to GitHub. A trigger fires from one place; an action lands in another.
2chat triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
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 2chat and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business GitHub.