Skip to content
Notis

Estimate removal costs when GitHub creates a deployment

Bring a removal cost estimate into the deployment moment, with the quantity and method defined in your automation instructions.

Trigger

New Deployment Created

Triggers when a new deployment is created in a GitHub repository. Fires an event for each newly created deployment detected in the configured repository. Deployments can optionally be filtered by target environment. The payload includes the deployment ID, commit SHA, ref, task, environment, creator details, and timestamps.

Action

Get CDR Price

Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.

Why this helps

A deployment can prompt sustainability follow-up, but the estimate often gets postponed while context shifts to the next task.

  • Request an estimate when a deployment is created.
  • Keep the estimate tied to a deployment event.
  • Specify a consistent removal method and amount in the prompt.

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 specifying the CDR method and amount to estimate.
  • 3Pick the New Deployment Created trigger for the relevant repository.
  • 4Choose where Notis should send run reports.
  • 5Test with one real deployment event.

Questions about this workflow

Does deployment creation mean the deployment succeeded?

No. This event means a deployment was created. Use a deployment status trigger if you want to respond to a reported status transition.

Can Notis infer the deployment's emissions?

The listed deployment event includes deployment metadata, but does not specify emissions. Supply a removal amount in your prompt or use a data source that provides it.

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.

TriggerScheduled

Get CDR Price

Tool to retrieve the cost of carbon dioxide removal. use after specifying cdr methods and amounts to estimate pricing.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

TriggerPolling

Get Pricing and Billing Info

Tool to get current pricing, fees, and billing thresholds for carbon removal. use when calculating costs before purchase.

ActionInstant

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.

TriggerPolling

Post CDR Purchase

Tool to initiate the purchase of carbon dioxide removal credits. use after confirming cost and methods to finalize the order.

ActionInstant

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.