Turn issue milestones into communication cues
A small timeline event can change what customers should expect. Make it easier to notice.
Trigger
New Issue Event
Triggers when a new issue event occurs in a GitHub repository. Covers all issue timeline events such as issues being closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, renamed, locked, or unlocked. Events can optionally be filtered by type. The payload includes the event type, timestamp, the actor who triggered the event, the affected issue details, and any associated commit references.
Action
Get Posts
Tool to retrieve a list of posts. use when you need ids and titles of posts for further operations.
Why this helps
Assignments, closures, and reprioritization often happen quickly, while the related customer message stays untouched.
- Make important issue activity easier to notice.
- Reduce forgotten communication after decisions change.
- Support cleaner customer expectation management.
- Replace memory-based follow-up with a useful cue.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Beamer to Notis once through the portal.
- 2Create a portal automation with a plain-language instruction to retrieve relevant Beamer posts.
- 3Choose the GitHub new issue event trigger.
- 4Select your run-report channel and test with one timeline event.
Questions about this workflow
Which timeline events are covered?
The trigger covers events such as closing, reopening, assignment, labeling, milestones, renaming, and locking.
Can I focus on one event type?
Yes. Configure the GitHub trigger with the issue event type you care about.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Beamer. A trigger fires from one place; an action lands in another.
GitHub triggers
Beamer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Count Posts
Tool to count existing posts. use when you need the number of posts matching specific filters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Category
Tool to retrieve a specific category by its id. use when you need to load metadata for a category before filtering or grouping posts by that category.
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 Feed
Tool to retrieve the url for your standalone feed. use after embedding to fetch the feed link for embedding or sharing.
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 Feeds
Tool to retrieve the url for your feed. use when you need to embed or access your standalone feed.
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 Feed URL
Tool to retrieve the url for your personalized feed. use after setting segmentation or language options to embed or redirect users.
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.
Get Notification
Tool to retrieve details of a specific notification by its unique notification id. use after obtaining the notification id to fetch its full details.
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 Notifications
Tool to fetch unread notifications. use after providing user context to retrieve and mark notifications as read.
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 Post Comments
Tool to retrieve comments for a specific post. use after identifying the post id to list its comments.
Connect any two apps with Notis in the middle.
GitHub and Beamer, 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 Beamer.