Recheck solar availability when plans change
When a Jira issue changes its schedule or site details, have Notis request a fresh hourly PV forecast for the stated location.
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
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.
Why this helps
A changed schedule can make an earlier view of solar availability less useful for the decision at hand.
- Recheck hourly PV output when relevant planning details change.
- Keep forecasts tied to the updated Jira issue context.
- Report when changed issues do not include a location.
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 request an hourly PV forecast when an updated issue changes its schedule or site details and includes a specific location.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real updated planning issue that includes a location.
Questions about this workflow
Will every issue edit request a new forecast?
Use the instruction to request a forecast only when schedule or site details relevant to the plan change.
Can Corrently forecast a location that is not in the issue?
The forecast needs a specific location. Instruct Notis to report missing location information rather than infer it.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
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.
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.