Turn Lemlist replies into owned GitHub follow-up
Every good reply gets a clear owner before it becomes another forgotten tab.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A founder sees an interesting reply, plans to follow up, then loses the thread among product and sales work.
- Assigns follow-up responsibility immediately
- Keeps outreach work beside the relevant product context
- Reduces memory-based task tracking
Setup
Build it in a few focused steps.
- 1Connect Lemlist and GitHub to Notis once through the portal.
- 2Create an automation in Automations -> New Automation, or ask Notis to create it.
- 3Use this plain-language instruction: When Lemlist sends a lead reply, assign the matching GitHub issue to the responsible teammate and include the conversation context.
- 4Choose notis_webhook as the trigger and select a channel for run reports.
- 5Send one real Lemlist reply through the webhook and confirm the GitHub assignment.
Questions about this workflow
Does Lemlist need a native Notis trigger?
No. Lemlist can send the event to a Notis webhook, which starts the automation.
Can Notis choose the assignee?
Yes. State the ownership rule in the plain-language instruction and Notis will interpret it.
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.