Show Better Stack monitors for a new GitHub pull request
Help reviewers notice operational risk before code reaches production.
Trigger
New Pull Request Created
Triggers when a new pull request is created in GitHub, matching the optional configured filters. Emits an event for each newly created pull request. Supports filtering by repository, owner/organisation, author, assignee, label, state, base branch, head branch, and draft status.
Action
List Monitors
Tool to list all monitors. use when you need to retrieve existing uptime monitors with optional filtering by url or name and pagination.
Why this helps
Reviewers may understand the code change but forget the service signals it could affect.
- Adds production awareness to review
- Reduces forgotten monitoring follow-up
- Keeps service context visible
Setup
Build it in a few focused steps.
- 1Connect GitHub and Better Stack to Notis once.
- 2Create a New Automation in the portal.
- 3Describe which monitors Notis should list for each new pull request.
- 4Choose New Pull Request Created and a report channel.
- 5Test with an actual pull request.
Questions about this workflow
Can I limit this to one repository?
Yes. Select the relevant GitHub trigger configuration and describe the service scope in your prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Better stack. A trigger fires from one place; an action lands in another.
GitHub triggers
Better stack actions
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.
Create Escalation Policy
Tool to create a new escalation policy. use when defining how incidents should escalate across team members.
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.
Create Heartbeat Group
Tool to create a new heartbeat group. use when you need to organize related heartbeat checks under a single, logical group. example prompt: "create a new heartbeat group named 'backend services'."
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Outgoing Webhook Integration
Tool to create a new outgoing webhook integration. use when you need to register an endpoint to receive event notifications from better stack.
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.
Create Source Group
Tool to create a new source group. use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
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.
Delete Escalation Policy
Tool to delete an escalation policy by id. use when you need to permanently remove an existing escalation policy after confirming its 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.
Delete Source Group
Tool to delete a source group by id. use when you need to permanently remove an existing source group after confirming it is no longer needed.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Get Heartbeat
Tool to get a single heartbeat by id. use when you need to fetch details of a specific heartbeat.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Heartbeat Availability
Tool to retrieve availability summary for a specific heartbeat. use when you need availability metrics for a heartbeat within an optional date range.
Connect any two apps with Notis in the middle.
Not just GitHub and Better stack. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Better stack.