Skip to content
Notis

Start a carbon removal purchase from an updated Jira issue

Keep a confirmed carbon removal decision moving by asking Notis to initiate the purchase from the updated Jira issue.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

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

Once a purchase decision is recorded, manually carrying it into a separate carbon removal service can stall the work.

  • Act on purchase intent recorded in an issue update.
  • Use the CDR purchase action for the request described in Jira.
  • Review the run report for the action result.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Cdr platform once in the Notis portal.
  • 2Create an automation in the portal, or tell Notis from any channel to create it.
  • 3In one instruction, ask Notis to initiate a CDR purchase only when the updated issue states confirmed method, amount, and purchase intent.
  • 4Pick the Jira Updated Issue trigger and choose where run reports go.
  • 5Test with one real updated issue containing confirmed purchase details.

Questions about this workflow

Will any issue update start a purchase?

The trigger fires for changes to issues in the configured Jira project. In your instruction, tell Notis to proceed only when the update states confirmed purchase intent and the required details.

What details are needed?

The issue should state the removal method, amount, and confirmed intent to purchase. Any other information required by the service must be supplied as well.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Cdr platform. A trigger fires from one place; an action lands in another.

Jira 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 Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get Pricing and Billing Info

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

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Post CDR Purchase

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

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Connect any two apps with Notis in the middle.

Jira 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.