Pull Render CPU usage when a GitHub check suite concludes
A green check suite means the code passed, but it says nothing about how the new build behaves under real load. Notis grabs your Render CPU usage the moment checks conclude, so a creeping spike shows up to you instead of to your users.
Trigger
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.
Action
Get CPU Usage
Tool to retrieve CPU usage metrics for Render resources. Use when you need to monitor CPU utilization for services, Postgres databases, or Redis instances. At least one filter (resource, service, or instance) must be provided.
Why this helps
Tests pass, you ship, and you have no idea the new build is quietly pinning CPU until things get slow. You only find out when something breaks, long after the check suite went green.
- See Render CPU behavior right after checks pass, not after an outage.
- Catch load-heavy changes before they degrade the experience.
- Turn a passing check suite into a real health readout.
- Remove one more thing you have to remember to look at manually.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Render to Notis once from the portal.
- 2Open your portal link and create a New Automation.
- 3Describe it plainly: when a GitHub check suite concludes, get my Render CPU usage and report it to me.
- 4Select the Check Suite Status or Conclusion Changed trigger and choose your channel.
- 5Re-run checks on a branch to confirm the CPU reading arrives.
Questions about this workflow
What time range does the CPU reading cover?
Notis pulls recent CPU usage by default. You can ask for a specific window in the plain-language instruction.
Can I watch a specific service?
Yes. Name the Render service in your instruction and Notis will target it.
Do I need to set thresholds?
No. Notis simply reports the usage. You can ask it to flag anything unusually high in plain language.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Render. A trigger fires from one place; an action lands in another.
GitHub triggers
Render 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.
Add Header Rule
Tool to add a custom HTTP header rule to a Render service. Use when you need to configure headers like Cache-Control, security headers, or CORS headers for specific request paths.
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.
Add or Update Secret File
Tool to add or update a secret file for a Render service. Use when you need to create a new secret file or update the content of an existing secret file.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add Resources to Environment
Tool to add resources to a Render environment. Use when you need to associate services, databases, Redis instances, or environment groups with an existing environment.
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.
Add Route
Tool to add redirect or rewrite rules to a Render service. Use when you need to configure URL routing, redirects, or rewrites for a service. Redirect rules send HTTP redirects to clients, while rewrite rules modify the request path internally.
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.
Create Custom Domain
Tool to add a custom domain to a Render service. Use when you need to configure a custom domain for a service.
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.
Create Environment Group
Tool to create a new environment group. Use when you need to create a shared collection of environment variables and secret files that can be used across multiple services.
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.
Create Environment
Tool to create a new environment within a Render project. Use when you need to set up a new environment for organizing services, databases, and other resources.
Commit Event
Triggered when a new commit is pushed to a repository.
Create Postgres Instance
Tool to create a new Postgres instance on Render. Use when you need to provision a new PostgreSQL database with configurable plan, version, and region.
Connect any two apps with Notis in the middle.
Not just GitHub and Render. Any combination from 985+ 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 Render.