Check GitHub merges before Findymail prospect follow-up
Know whether the promised fix shipped before you send the next message.
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
Founders promise updates to prospects but cannot remember whether the linked fix actually merged.
- Prevents premature updates
- Keeps promises grounded in delivery
Setup
Build it in a few focused steps.
- 1Connect Findymail and GitHub to Notis once.
- 2Create a new automation in the portal.
- 3Write one instruction to check whether promised prospect-related pull requests have merged.
- 4Choose a daily schedule and a reporting channel.
- 5Test with one known pull request.
Questions about this workflow
Can this send results to a channel?
Yes. Select the channel where you want Notis to report each run.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Findymail to GitHub. A trigger fires from one place; an action lands in another.
Findymail 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 Findymail and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.