Check whether monitored release pull requests have merged
When an Apify result references a pull request, let Notis check its GitHub merge status and report the result.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Tracking release references across collected pages and GitHub can create avoidable context switching.
- Quickly verify whether a referenced pull request has merged.
- Keep release monitoring results connected to GitHub status.
- Avoid manually opening each pull request to check its state.
Setup
Build it in a few focused steps.
- 1Connect Apify and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for release monitoring.
- 3Tell Notis to extract the repository and pull request number from each incoming Apify result, check whether it merged, and report the outcome.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real result containing a pull request reference.
Questions about this workflow
Does this workflow merge the pull request?
No. It checks whether the specified pull request has already merged.
What information must Apify send?
The result needs to identify the GitHub repository and pull request number.
Can a non-merged result mean the pull request does not exist?
The check action reports not merged or not found for its negative response, so Notis should describe that uncertainty in the report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Apify to GitHub. A trigger fires from one place; an action lands in another.
Apify triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Apify and GitHub, or any other 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.