Skip to content
Notis

Find greener operating windows while a site responds to an incident

Send an incident update with the affected site's postal code and flexible device loads. Notis can ask Corrently for an optimized energy schedule so your team has the next operating windows in one place.

Trigger

Webhook received

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

Action

Energy Schedule Computation

Why this helps

During an incident, facility teams may need to adjust flexible energy use while they are already coordinating a response.

  • Turn incident updates into a concrete schedule for flexible energy loads.
  • Keep device names, operating constraints, and site postal code together in the request.
  • Send a run report to the channel your team uses for incident coordination.

Setup

Build it in a few focused steps.

  • 1Connect Abuselpdb and Corrently once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis to use the incoming site's postal code and device constraints to request an optimized energy schedule in Corrently.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real example that includes a postal code and flexible device constraints.

Questions about this workflow

What starts this workflow?

An HTTP request to the Notis webhook starts it. Abuselpdb has no trigger events, so this workflow uses a Notis-native webhook.

What information does the webhook need?

Include the affected site's German postal code and the devices or loads that can be scheduled, with their operating constraints. Corrently's schedule action uses regional green power information.

Does Abuselpdb automatically send incident events to this workflow?

No Abuselpdb trigger events are listed. An external incident system or backend must send the webhook request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Abuselpdb triggers

Corrently actions

Recurring trigger

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

TriggerScheduled

CO₂ Meter Update

Creates or updates an electricity reading for CO₂ emissions tracking.

ActionInstant

Webhook trigger

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

TriggerInstant

PV Generation Forecast

Provides hourly solar generation forecasts for a location in Germany.

ActionInstant

Commit Strom-Quittung

Finalize an electricity receipt after collecting the seller, buyer, and transaction details.

ActionInstant

Geocode Location

Convert a place name or free-text location into geographic coordinates.

ActionInstant

Energy Schedule Computation

ActionInstant

Get Metering Reading

Retrieve an electricity meter reading with its green and grey energy split and CO2 emissions.

ActionInstant

Get Stromkonto Balances

Retrieve account balances for green energy bonuses, generation, self-consumption, offsets, and trees planted.

ActionInstant

Get Stromkonto Choices

Retrieve the available contract choices for an energy account.

ActionInstant

Connect any two apps with Notis in the middle.

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