Aggregator Node
Calls an HTTP endpoint with a payload assembled from its own inputs, and spreads the response across its outputs.
This is the node that connects an XGENIA frontend to a backend function — including the maths components you deploy to the RGS platform.
The Aggregator has no fixed ports. You declare them:
- Data Inputs — one input port per name. Whatever is connected to them becomes a field of the request body.
- Triggers — one signal input per name. Pulsing one sends the request; the trigger's name is sent with it, so one node can serve several operations.
- Outputs — one output port per name, filled from the matching key of the JSON response.
Nothing is sent until a trigger pulses. An Aggregator whose triggers are all unwired can never call anything, which is a silent failure in a browser and the reason Publish warns about it.
With deployed maths components
You rarely configure this by hand for RGS work. Two things produce a ready-made Aggregator:
- Publish replaces every instance of a deployed maths component with one, aimed at that component's live endpoint, with field names taken from the component's gateway ports verbatim.
- Dragging a component out of Maths RGS → Deployed drops one already pointed at the live endpoint.
An Aggregator dropped from the Deployed tab calls the live backend from the editor preview too. If the component has a bet/win mapping, previewing it moves balances and writes real rounds. See Maths Components.
The request also carries reserved identity fields — a per-browser client id, a per-tab session id, and a player id when the graph knows one — which is what lets the platform attribute a round. See Round tracking.
Inputs
General
| Data | Description |
|---|---|
| URL (string) | The endpoint to POST to. |
Configuration
| Data | Description |
|---|---|
| Data Inputs (stringlist) | Names of the data input ports to create. Each becomes a field of the request body. |
| Triggers (stringlist) | Names of the trigger signals to create. Pulsing one sends the request. |
| Outputs (stringlist) | Names of the output ports to create. Each is filled from the matching response key. |
A response cannot carry a signal, so a deployed component's own Done/Success signal outputs wire to the Aggregator's success output instead — the reply arriving is the pulse. A port named for failure wires to failure.