Check GitHub pull request merge status from Typeform
Make a launch dependency visible before it becomes a surprise.
Trigger
New Form Response
Triggers when a respondent completes and submits the form.
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
Launch readiness depends on details that are easy to assume rather than verify.
- Reduces launch uncertainty
- Creates a clear status check
Setup
Build it in a few focused steps.
- 1Connect Typeform and GitHub to Notis once.
- 2Create a New Automation in the portal.
- 3Tell Notis to check whether the required pull request is merged when the launch form arrives.
- 4Select New Form Response and a report channel.
- 5Test with a pull request whose status you know.
Questions about this workflow
Will this merge the pull request?
No. It checks whether the specified pull request has already merged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Typeform to GitHub. A trigger fires from one place; an action lands in another.
Typeform 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.
New Form Response
Triggers when a respondent completes and submits the form.
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.
Typeform 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.