Keep release audience decisions aligned with PR changes
Scope changes should update the communication context before launch day arrives.
Trigger
Pull Request Updated
Triggers when an existing pull request is updated in a GitHub repository. Updates include title edits, description changes, label changes, assignee changes, reviewer requests, draft status changes, base branch changes, being closed, merged, or reopened. Only pre-existing PRs that receive an update will fire the trigger; newly created PRs are excluded. Supports optional filters: state, base branch, head branch, author, label, and draft status.
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
A pull request can change substantially while the planned audience and message remain based on the old scope.
- Refreshes audience options after meaningful PR updates
- Supports clearer release segmentation decisions
- Reduces the mental burden of tracking scope changes manually
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 in plain language.
- 3Tell Notis: when an existing customer-facing pull request is updated, retrieve Sendlane custom fields relevant to its current release scope.
- 4Select the GitHub pull request updated trigger and choose the reporting channel.
- 5Test with one active pull request update.
Questions about this workflow
Which pull request updates are covered?
The trigger can cover title, description, labels, reviewers, draft status, base branch, closure, merge, and other supported updates.
Can I limit this to a release branch?
Yes. State the branch convention in the instruction and use the trigger filters available for the monitored pull request.
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.