Slots & Styling
Every attribute, method and event of <rapi-flow> is on its API reference page, read from the element’s source. All its events bubble and cross the shadow boundary (composed).
Put your own markup at the top or bottom of the element with slot="header" or slot="footer": a logo, a title, a server switch, links. It stays in the page’s DOM, so the page’s CSS styles it and its scripts find it, and it scrolls with the diagram. Its spacing is yours: the element adds none around it.
<rapi-flow arazzo-url="/workflows/ship-a-parcel.arazzo.yaml" for="thedoc"> <div slot="header"> <img src="/logo.svg" alt="Rapid Parcels" height="28"> </div> <p slot="footer">Questions? <a href="/support">Contact support</a>.</p></rapi-flow>| Slot | Where |
|---|---|
header |
At the top, above the card with the Arazzo document’s URL and API sources. |
footer |
At the bottom, below the run panel. |
The rapi-flow example puts the <rapi-flow> logo and its Real / Mock server switch in the header slot; the multi-API example, the Rapid Parcels logo.
Styling
Section titled “Styling”theme and color-scheme work as on <rapi-doc>, and the element reads the same CSS custom properties. Its CSS parts: mcp-export, document (the card with the URL and the API sources), sources, url, url-form, url-input, url-load, url-error, header, title, select, description, view-toggle, diagram, run, run-inputs, run-button, run-stop, log-toggle (the Execution Log’s Single line / Multiline switch), message, problems.
rapi-flow::part(diagram) { max-height: 32rem;}Properties
Section titled “Properties”The element also exposes arazzoDocument (the parsed document), workflowRuntimeSource, which a paired <rapi-doc> uses to add workflow tools to its MCP export, and the statusCodes property that fills the Mock Response Status table (see Running against a mock).