Skip to content
Notis

Keep Corrently readings current as Jira data changes

When a Jira issue changes, have Notis check whether its electricity consumption reading was revised and update the corresponding Corrently meter.

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

CO₂ Meter Update

Tool to create or update a co₂ meter reading for emissions tracking. use when sending new or updated electricity consumption readings to corrently.

Why this helps

A corrected consumption figure in Jira can leave a stale value in your emissions tracking.

  • Catch revised consumption figures from existing issues.
  • Keep the Jira change and Corrently reading in the same workflow.
  • Surface changes that need more context in run reports.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Corrently once in the Notis portal.
  • 2Create an automation and give it a clear name.
  • 3In one instruction, tell Notis to check updated issues for changed electricity consumption readings, update the relevant Corrently meter when the issue provides enough context, and report ambiguity.
  • 4Pick Jira Updated Issue as the trigger and choose where run reports go.
  • 5Test with one real updated issue containing a revised reading.

Questions about this workflow

Does this trigger on Jira comments?

No. The Updated Issue event covers changes to an issue and does not fire on comment activity.

How should Notis handle a changed issue with no new reading?

Tell Notis to leave the Corrently meter unchanged and report that no usable reading was provided.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Corrently actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

CO₂ Meter Update

Tool to create or update a co₂ meter reading for emissions tracking. use when sending new or updated electricity consumption readings to corrently.

ActionInstant

Webhook trigger

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

TriggerInstant

PV Generation Forecast

Tool to get solar energy production forecasts (hourly output and loss estimates) for a specific location. use when you need hourly pv generation data to optimize energy scheduling.

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

New Project

Triggered when a new project is added in Jira

TriggerInstant

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 Corrently, 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 Corrently.