Compare customer segments before choosing a focus
Turn a rough audience question into a clear comparison tied to the product priorities that matter.
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
Compare options
Weigh several products, vendors, or approaches.
Why this helps
Customer segment choices stay vague when teams lack one place to compare fit, evidence, and priorities.
- Compares the segments against the product priorities in the issue.
- Flags missing evidence so the next research step is explicit.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Deep research in the Notis portal.
- 2Prompt Notis: When a new issue names customer segments, compare them against the supplied product priorities and answer the issue question with sources, explicitly flagging missing evidence.
- 3Select New Issue Created, choose email for reports, and create the automation.
- 4Test with one issue naming two segments, product priorities, and a concrete comparison question.
Questions about this workflow
What should the issue include?
Include the segments, product priorities, and comparison question; the report flags evidence that is missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Deep research. A trigger fires from one place; an action lands in another.
GitHub triggers
Deep research actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Research a company
Get a sourced brief before a call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Compare options
Weigh several products, vendors, or approaches.
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.
Deliver it later
The report arrives as a follow-up message when it is ready.
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 Deep research, 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 Deep research.