IRIS
How this page works

A transformer plugin is an independently deployed HTTP service — a tone-of-voice rewrite, an enrichment step — that the Substation calls while delivering a page. Register one here and it runs for this tenant without any change to the Substation's own code.

Every plugin implements the same contract: POST {url}/transform (data and context in, transformed data out) and GET {url}/health. Plugins run in stage order, then by order within a stage (ascending).

A plugin at stage Block never runs page-wide: it runs only on the blocks of schematics whose manifest declares it under transformers, with the schematic's config merged over the plugin config registered here.

Test calls the plugin's health endpoint by name — the stored API key stays on the server and never appears in this page.

Configured plugins (0)

No transformer plugins yet

Optional — register an external service to run at a pipeline stage for this tenant.

+ Add plugin

Add a plugin for "all"

This tenant has no environments yet — the resource applies to all of them.

Request signing and resilience

HMAC secret for the X-Signature request header; without one the Substation signs with the API key. Write-only — never shown again after saving.

100–120000 ms. Blank uses the default.

Failure rate that opens the breaker, 1–100.

How long an open breaker waits before trying again, 1000–600000 ms.

Cancel

Recent calls

The last 20 calls the Substation made to this tenant's plugins while delivering pages — to spot a plugin that is failing, slow or never called. Request and response contents are not shown.

No plugin calls recorded yet for this tenant.