Integration
Connect Open Government, ACT to GrünstromIndex
When something happens in Open Government, ACT, your agent does the next thing in GrünstromIndex. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Open Government, ACT and GrünstromIndex to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Open Government, ACT and GrünstromIndex
Triggers and actions 1 trigger · 6 actions
Trigger
New record in datasetPolling trigger that fires when new rows are published to a specified ACT open-data dataset.
- Find datasets
Search the ACT Government open-data catalog for published datasets by keyword, category, or tag (Socrata catalog API).
- Get dataset metadata
Retrieve a dataset's metadata — column schema, description, publisher, update frequency — for a given ACT open-data dataset id.
- List dataset records
Retrieve rows from a specific ACT open-data dataset, with optional filtering, sorting, and paging (Socrata SODA resource API).
Action
Get best hour for green energy useFind the best upcoming hour to consume electricity based on renewable-energy availability for a German postal code, within a configurable lookahead window. GET /v2.0/gsi/bestHour (params zip, timeframe).
- Get current GrünstromIndex
Get the current GrünstromIndex value (share of renewable energy right now) for a German postal code. GET /v2.0/gsi/pps (param zip).
- Get green energy forecast
Fetch the 72-hour GrünstromIndex forecast (share of renewable energy, CO2 intensity, and pricing signal) for an address or place name. GET /v2.0/gsi/prediction (query param q).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.