Know when customer-linked code is actually merged
Replace mental reminders with a clear status check tied to the customer conversation.
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 founder promises an update, but the related pull request status requires another manual lookup.
- Keeps customer commitments tied to delivery status
- Prevents premature updates
- Creates a focused exception signal
Setup
Build it in a few focused steps.
- 1Connect Lemlist and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it in plain language.
- 3Tell Notis: When a Lemlist customer milestone is received, check whether the linked GitHub pull request is merged and report if it is still open.
- 4Choose notis_webhook and select the channel for run reports.
- 5Test with one real customer milestone.
Questions about this workflow
Does it merge the pull request?
No. It only checks whether the specified pull request has already merged.
Can it report only unfinished work?
Yes. State that Notis should report only when the pull request is not merged.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Lemlist to GitHub. A trigger fires from one place; an action lands in another.
Lemlist 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 Lemlist and GitHub. Any 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.