Integration
Connect Particle to GrünstromIndex
When something happens in Particle, 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 Particle 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 Particle and GrünstromIndex
Triggers and actions 1 trigger · 8 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
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).
Action
Get current GrünstromIndexGet the current GrünstromIndex value (share of renewable energy right now) for a German postal code. GET /v2.0/gsi/pps (param zip).
Action
Get green energy forecastFetch 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.
Each app on its own
Reviews