Skip to main content
Use case

Automation Agency: one sentence of process description — a tested workflow draft for § 14a EnWG

The people who own the process describe it in one sentence — the agency turns it into a workflow draft for the native Workflow Builder. Six roles work in sequence: intake, architect, engineer, QA, compliance review, delivery. The graph is validated against the pre-flight check and test-run in the engine’s simulation mode before a human ever sees it. Every side-effecting node is stubbed during that run — no customer, installer or supplier receives a message. The agency never activates anything; a tenant_admin approves.

One sentence
a process description in plain language instead of nodes and edges
Test run
in the engine's simulation mode — every side-effecting node is stubbed
Draft only
activation by a tenant_admin only — never by the agency
The starting point

Since 1 January 2024 every new controllable consumption device — heat pump, wallbox, storage — has to be registered, checked and assigned a network-charge reduction module under § 14a EnWG. For a municipal utility that is a volume process with direct customer impact: check the grid connection point, assign the module, chase the installer for missing data, inform customer and supplier, document the case. The department knows exactly how it runs — nobody there can build it.

How it works
1

Describe the process in one sentence

No diagram, no nodes: you write what should happen. The agency derives the trigger, the required capability and the actions — and asks a question instead of guessing when the description is ambiguous.

2

Build, validate, test-run

The engineer generates the graph strictly from allow-listed node types; shell execution is barred. Validation errors go back to him, bounded to a few rounds. Then the workflow runs in simulation mode — side-effecting nodes return stubs instead of real sends.

3

Read the review summary and approve

The reviewer lists what has outside effect, what is still missing and what a human has to look at — including honest open points instead of invented recipient lists. Only then does a tenant_admin decide: approve, or approve and activate.

The outcome
One sentence
a process description in plain language instead of nodes and edges
Test run
in the engine's simulation mode — every side-effecting node is stubbed
Draft only
activation by a tenant_admin only — never by the agency
Grounded in

The process rests on § 14a EnWG (grid-oriented control of controllable consumption devices) and the BNetzA Festlegung BK6-22-300 of 27 November 2023, binding for new controllable devices since 1 January 2024. The agency’s guarantees live in code, not in a prompt: draft instead of activation, simulation mode instead of real side effects, a fixed list of permitted node types. Demo with sample data; the utility is fictional. The generated workflow is a draft and replaces no professional review.

Book a demo

See it on your own use case.

30 minutes, scoped to your industry, frameworks and integrations. You leave with a concrete scenario — not a sales loop.