Check whether the pull request mentioned on a call merged
Follow up on a call about a change by checking the merge status of the GitHub pull request it names.
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
A verbal update about a code change can leave the caller and team unsure whether the pull request actually merged.
- Verify a pull request's merge status against GitHub.
- Keep the call reference and status check in one Notis run report.
- Avoid treating a verbal estimate as confirmation of a merge.
Setup
Build it in a few focused steps.
- 1Connect Bland AI and GitHub once in the Notis portal.
- 2Create an automation from any channel or in Automations, New Automation; name it and write its prompt.
- 3In one instruction, ask Notis to check the merge status of the pull request identified in the Bland AI webhook and report the result.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with a real call webhook containing a repository and pull request number.
Questions about this workflow
Does this check whether the pull request is approved?
No. The available GitHub action checks whether a specified pull request has been merged.
What information must the webhook include?
It must provide enough information to identify the repository and pull request number.
Does this send a response to the caller?
No. The workflow reports its run result to the report channel you choose.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bland AI to GitHub. A trigger fires from one place; an action lands in another.
Bland AI 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.
Bland AI 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.