Output Parser

Turns an LLM's raw text answer into validated structured JSON. Strips a ```json code fence, pulls the first {…} / […] out of surrounding prose, and JSON-parses it; in schema mode it also validates the result against a JSON Schema. Emits { parsed, valid } (plus an error when invalid) — pure, no model call.

Finding it in the library

Search the builder's node library for Output Parser (it lives under Processing). A single click opens the in-editor docs panel shown here — description, ports, and every property, without leaving the canvas. Double-click (or drag) to add it to the workflow.

Wired up in the builder

Output Parser in a real, runnable flow — captured live from the Studio editor, exactly as it looks on your canvas. This is the same workflow used for the example input & output below.

How it’s configured

The node’s settings as the builder shows them — every field laid out with real values. In the Studio these are edited on the node: click the chevron on the divider under its ports to open them.

Ports

Ports are the node’s contract with its neighbours. In the editor a port label renders bold when wired and italic when optional; ◈ ports accept attachment carriers rather than data wires.

How data flows through it

Output Parser consumes the content of the incoming envelope — when it is fed directly by a trigger, the trigger’s wrapper is unwrapped at the node boundary so the node sees the actual data, not the metadata shell. Its output becomes the payload for the next node, while the envelope (trace ids, correlation, binary refs) rides along untouched. In the Runs view you always see the whole envelope for both sides of this node.

Expressions in the config

None of this node’s properties are string-typed, so {{ }} expressions don’t apply here — JSON- and code-typed fields are always taken literally.

Build it with AI

Every node in this reference is reachable through Flowdrome’s AI Copilot and the MCP tools — say what you want, and the graph surgery happens server-side. Node types resolve fuzzily, so the catalog label (Output Parser) works as well as the exact type id (processing.output-parser).

In the Copilot panel (or any connected AI):

add a output parser node after the trigger

As a step in a create_chain_workflow call:

{"type":"Output Parser","config":{}}

curl -s -X POST http://localhost:4800/mcp -H "content-type: application/json" -d '{ "jsonrpc": "2.0", "id": "1", "method": "tools/call", "params": { "name": "add_node", "arguments": { "workflowId": "<id>", "type": "Output Parser" } } }'

Example input & output

Captured from a real test run of the workflow above — this is what the Runs view shows after pressing Test workflow.

Input — what the node received

Output — what the node produced

Property reference

Every setting, with its type and default — the same fields shown configured above.

Related nodes

The rest of the Processing group — the same folder you’d scan in the editor’s library.

• Validate JSON Schema Validates input with an inline or context-provided JSON Schema.
• Map Fields Builds a new JSON object by copying source paths to destination paths.
• Modify Set, rename, remove, or keep fields with {{ }} expressions, type coercion, and dot-paths.
• Edit Fields (Set) Set output fields from literals or JS {{ }} expressions, per item
• JSON To XML Converts a JSON value to an XML document with a configured root element.
• XML To JSON Parses an XML string into a JSON object (xml2js-style: attributes under $, repeated elements become arrays).
• XBRL Reads an XBRL or inline-XBRL (iXBRL) filing — SEC 10-K/10-Q, EU ESEF, UK accounts — and returns its facts as s
• Check Checks incoming data, including request headers, and routes to valid or invalid.

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The screenshots and example data are captured from a live Flowdrome by npm run shots:nodes and npm run gen:examples.