Keep changing pull requests aligned with audience data
When the implementation changes, the customer communication context can stay current too.
Trigger
New Commit Added to Pull Request
Triggers when a new commit is pushed to a specific pull request. Monitors all commits on the specified pull request and emits an event for each newly added commit. This covers force-pushes and additional commits pushed to the PR's head branch.
Action
Get custom fields list
Tool to retrieve a list of custom fields. use when you need to list all custom fields with optional pagination.
Why this helps
Repeated PR changes make it hard to remember which segmentation options are already available.
- Refreshes field context during active product work
- Supports better segmentation without extra research
- Reduces cognitive load during iterative releases
Setup
Build it in a few focused steps.
- 1Connect GitHub and Sendlane to Notis once through the portal.
- 2Create the automation in the portal, or ask Notis to set it up conversationally.
- 3Tell Notis: when a new commit is added to a customer-facing pull request, retrieve Sendlane custom fields relevant to the planned announcement.
- 4Select the GitHub new commit added to pull request trigger and choose a report channel.
- 5Test with one new commit on an active pull request.
Questions about this workflow
Could this be noisy on active pull requests?
Use the instruction to limit it to labeled or otherwise customer-facing pull requests.
What does Notis return?
It retrieves the current Sendlane custom field list and reports the useful context in your chosen channel.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get custom fields list
Tool to retrieve a list of custom fields. use when you need to list all custom fields with optional pagination.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create List
Tool to create a new list. use when you need to add a brand-new mailing list before sending campaigns.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Sendlane, 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 Sendlane.