Check Cdr platform health after deployment status changes
Use a GitHub deployment status event to check that the Cdr platform service and its core connections are responding.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Get Health Check
Tool to perform a health check of the cdr platform service. use when you need to verify api and database connectivity and core service status.
Why this helps
When an integration is needed for a time-sensitive sustainability task, finding out it is unavailable only after starting can add friction.
- Check API and database connectivity at a deployment status milestone.
- Get a service status report without opening another dashboard.
- Use health results to decide whether to continue with a separate CDR task.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Cdr platform once in the Notis portal.
- 2Create an automation with a name and a prompt to run the Cdr platform health check and summarize the result.
- 3Pick the New Deployment Status Created trigger for the relevant deployment.
- 4Choose where Notis should send run reports.
- 5Test with one real deployment status event.
Questions about this workflow
Does the health check confirm a purchase can be completed?
It checks service, API, database connectivity, and core service status as described. It does not guarantee a specific purchase will succeed.
Can it run only for successful deployment statuses?
The event is for newly created deployment statuses. Use only trigger options that Notis exposes; the supplied event description does not define a status filter.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Cdr platform. A trigger fires from one place; an action lands in another.
GitHub triggers
Cdr platform actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get CDR Price
Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Health Check
Tool to perform a health check of the cdr platform service. use when you need to verify api and database connectivity and core service status.
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 Pricing and Billing Info
Tool to get current pricing, fees, and billing thresholds for carbon removal. use when calculating costs before purchase.
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.
Post CDR Purchase
Tool to initiate the purchase of carbon dioxide removal credits. use after confirming cost and methods to finalize the order.
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 Cdr platform, 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 Cdr platform.