Fetch Render deploy history when a GitHub pull request opens
Reviewing a pull request without knowing what is currently deployed means guessing. Notis watches GitHub for new pull requests and, the instant one opens, hands you the latest Render deploy list so you review with the full picture already in front of you.
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 Deploys
Tool to list recent deploys for a Render service with pagination and filtering. Use when you need to fetch deploy history, inspect deploy statuses, or find a specific deployId to pass to other deploy operations.
Why this helps
You open a pull request to review it, then have to leave GitHub, log into Render, and dig through deploy history just to remember what version is actually live. That tab-hopping breaks your focus every single time.
- See what is currently deployed to Render before you start reviewing code.
- Skip the manual login-and-dig routine every time a pull request lands.
- Keep code review and deploy state in one place instead of two browser tabs.
- Catch a stale or failed deploy before you approve new changes on top of it.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Render to Notis once from the portal integrations screen.
- 2Ask Notis to send you your portal link, then open Automations and choose New Automation.
- 3Write the plain-language instruction: when a new pull request is created on GitHub, list the recent Render deploys and send them to me.
- 4Pick the New Pull Request Created trigger and choose the channel where Notis should report each run.
- 5Open a test pull request and confirm the Render deploy list arrives in your channel.
Questions about this workflow
Do I have to map any fields between GitHub and Render?
No. You describe the outcome in one sentence and Notis handles the rest. There are no field-mapping screens to configure.
Which pull requests trigger this?
Every newly created pull request in the repository you connected fires the automation. You can narrow it in plain language if you only care about a specific base branch.
Where do the Render deploys show up?
Wherever you point the automation. Notis can report runs to Telegram, WhatsApp, email, or another connected channel.
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.