Connect Jira to Corrently

When something happens in Jira, Notis takes the next step in Corrently. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Jira to Corrently

View example

Track Energy Usage from Jira Issues

Turn Jira issues that contain electricity consumption readings into Corrently CO₂ meter updates.

View example

Refresh CO₂ Records When Jira Readings Change

Update Corrently meter readings when an existing Jira issue is changed to include revised electricity consumption data.

View example

Add Solar Forecasts to Site Planning Issues

Use new Jira planning issues with a site location to request Corrently hourly PV generation forecasts.

View example

Refresh Solar Forecasts After Schedule Changes

When a Jira issue changes with a revised energy schedule or site location, retrieve an updated Corrently PV forecast.

View example

Get a Solar Outlook for New Jira Projects

Request a Corrently PV forecast when a newly created Jira project includes a specific site location.

View example

Send Scheduled Energy Readings to Corrently

On a recurring schedule, process electricity consumption readings supplied to Notis and update Corrently CO₂ meters.

View example

Review Hourly Solar Forecasts on a Schedule

Get recurring Corrently PV generation forecasts for specified locations to support energy scheduling reviews.

View example

Update Corrently from an Incoming Energy Reading

Start a meter update when an HTTP request sends an electricity consumption reading and sufficient meter context.

View example

Fetch a Solar Forecast from a Site Request

Use an incoming HTTP request with a specified site location to retrieve a Corrently hourly PV forecast.

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

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.