Connect new issues with existing feedback threads
Before you start solving a new issue, see whether customers have already described the problem elsewhere.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Get Post Comments
Tool to retrieve comments for a specific post. use after identifying the post id to list its comments.
Why this helps
The same request or pain point may be discussed in Beamer while the GitHub issue looks like a brand-new task.
- Expose related feedback earlier.
- Reduce duplicate issue investigation.
- Help product decisions start with evidence.
- Keep customer language close to engineering work.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Beamer to Notis once through the portal.
- 2Create the automation in the portal with one plain-language instruction for retrieving related comments.
- 3Select the new issue created trigger.
- 4Choose the channel for run reports and test with one issue.
Questions about this workflow
How is this different from new issue triage?
This workflow focuses specifically on retrieving Beamer comments to find existing feedback threads.
Are pull requests included?
No. The trigger excludes pull requests and monitors true issues only.
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.