Keep customer follow-up synchronized with issue updates
The latest issue context can quietly change who needs to hear from you.
Trigger
Issue Updated
Triggers when an existing issue is updated in a GitHub repository. Monitors issues for any changes such as title edits, body edits, label changes, assignee changes, state transitions (opening, closing, reopening), milestone updates, and comment additions. Only pre-existing issues that receive updates are emitted; newly created issues are excluded. Pull requests are also excluded -- only true issues fire events.
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
Updated feedback and requests often change the audience, but no one refreshes the segmentation context.
- Keeps follow-up planning connected to the latest issue details
- Reduces stale audience assumptions
- Creates a reliable checkpoint after issue activity
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 create it conversationally.
- 3Tell Notis: when an existing customer-facing issue is updated, retrieve Sendlane custom fields and summarize options for the next customer update.
- 4Choose the GitHub issue updated trigger and select the run-report channel.
- 5Test with one existing issue update.
Questions about this workflow
How is this different from the new issue workflow?
This one responds only to updates on existing issues, so it supports ongoing feedback and follow-up.
Can comments count as updates?
The GitHub trigger includes issue updates such as comment additions.
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.