Purchase preapproved carbon removal from a release issue
Turn a clearly labeled release planning issue into a defined carbon removal order, using a prompt that includes the method, amount, and cost confirmation steps.
Trigger
New Issue Created
Triggers when a new issue is created in a GitHub repository. Pull requests are automatically excluded -- only true issues produce events. Results can be filtered by labels, assignee, creator, and mentioned user. The payload includes the issue number, title, body, state, labels, assignees, comment count, creator details, timestamps, and direct links to the issue on GitHub.
Action
Post CDR Purchase
Tool to initiate the purchase of carbon dioxide removal credits. use after confirming cost and methods to finalize the order.
Why this helps
A planned sustainability commitment can stall between an issue being filed and someone returning to complete the order.
- Connect a new planning issue to a defined order instruction.
- Require cost and billing review before purchase in the automation prompt.
- Get the order result in a report channel for follow-up.
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 purchase method, amount, and required price and billing checks before ordering.
- 3Pick the New Issue Created trigger for the relevant repository and use available trigger options to target planning issues.
- 4Choose where Notis should send run reports.
- 5Test with one real issue and review the resulting run report.
Questions about this workflow
Will this purchase whenever any issue is created?
It should be scoped using trigger options that are actually available, and the prompt should clearly describe the intended issue and exact order. The listed event supports filtering by labels and other issue attributes.
What needs to be specified before placing an order?
State the CDR method and amount in the prompt, and require the price estimate and billing information to be reviewed before the purchase action. Do not treat issue content as a verified order quantity by itself.
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.