Confirm payment portal fixes are merged
Close the loop on customer-impacting fixes with a verified merge status.
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
Teams tell customers a fix is coming without confirming the code actually merged.
- Improves customer communication
- Prevents premature closure
- Provides a clear release signal
Setup
Build it in a few focused steps.
- 1Connect Chaser and GitHub in Notis once.
- 2Create an automation for payment portal incident fixes.
- 3Tell Notis to check the linked pull request merge status when Chaser reports the incident.
- 4Pick the Chaser webhook trigger and choose where reports go.
- 5Test with one real pull request.
Questions about this workflow
Can it notify the customer directly?
This workflow reports merge status to your chosen channel; customer communication remains under your control.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Chaser to GitHub. A trigger fires from one place; an action lands in another.
Chaser 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.
Chaser 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.