Keep outreach aligned with what your README now says
Your README is often the clearest explanation of the product. When it changes, Notis can keep the relevant Lemlist context from going stale.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Add Variables to Lead
Tool to add one or more variables to a lead. use when you need to enrich a lead with custom data after its creation or retrieval.
Why this helps
Outreach references old positioning or setup instructions after documentation changes.
- Keeps messaging aligned with public documentation
- Reduces repeated explanation work
- Preserves a reliable source of context
Setup
Build it in a few focused steps.
- 1Connect GitHub and Lemlist to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to refresh relevant Lemlist lead context after a README change.
- 3Select the GitHub Repository README Changed trigger and choose the channel for run reports.
- 4Test it with one README update.
Questions about this workflow
Can this watch a specific branch?
Yes. Include the repository directory and branch or tag in the instruction.
Does it contact everyone who has been emailed?
Only the leads and scope you describe in the automation prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Lemlist. A trigger fires from one place; an action lands in another.
GitHub triggers
Lemlist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Schedule
Tool to delete a specific schedule by scheduleid. use when you need to remove a schedule permanently after confirming its id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Unsubscribed Email
Tool to delete an email from the unsubscribed list. use when restoring a subscriber who has opted back in and you need to remove them from the suppressed contacts.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Unsubscribe Lead From Campaign
Tool to unsubscribe a lead from a campaign. use when you need to stop further outreach by removing a lead from the specified campaign.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Get All Webhooks
Tool to retrieve the list of all webhooks configured for the team. use when you need to sync or audit active webhooks.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Campaign By ID
Tool to retrieve a specific campaign by campaignid. use when you need detailed campaign information by id.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Start Campaign Export
Tool to start an asynchronous export of all campaign statistics (csv). use when you need to initiate a csv export for a given campaign and track its progress.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Get Campaign Export Status
Tool to check the status of an asynchronous campaign export. use after starting an export to poll until done or error.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Get Campaign Sequences
Tool to retrieve a list of all sequences for a campaign with steps and conditions. use after fetching campaign to inspect its nested sequences and branching rules.
Connect any two apps with Notis in the middle.
GitHub and Lemlist, 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 Lemlist.