Give every shipped feature a Sendlane audience home
When code ships, the customer follow-up is already waiting for you.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
Create List
Tool to create a new list. use when you need to add a brand-new mailing list before sending campaigns.
Why this helps
Founders finish the technical work but lose momentum before preparing the announcement audience.
- Turns completed engineering work into a communication cue
- Creates separate audience containers for major shipped changes
- Protects post-launch follow-through during busy weeks
Setup
Build it in a few focused steps.
- 1Connect GitHub and Sendlane to Notis once through the portal.
- 2Create a new automation in the portal, or ask Notis in plain language.
- 3Tell Notis: when a customer-facing pull request is merged, create a Sendlane list named for the shipped feature or release.
- 4Choose the GitHub pull request event trigger and a reporting channel.
- 5Test it using one recently merged customer-facing pull request.
Questions about this workflow
Can this ignore internal-only pull requests?
Yes. Include your label, branch, or naming convention for customer-facing work in the instruction.
What happens after the list is created?
Notis reports the run in your selected channel. You can then use the list in Sendlane.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Sendlane. A trigger fires from one place; an action lands in another.
GitHub triggers
Sendlane actions
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.
Get custom fields list
Tool to retrieve a list of custom fields. use when you need to list all custom fields with optional pagination.
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.
Create List
Tool to create a new list. use when you need to add a brand-new mailing list before sending campaigns.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Connect any two apps with Notis in the middle.
Not just GitHub and Sendlane. 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 Sendlane.