Parsing blocks
Parser output is a named user variable . It may also be captured when capture is enabled. The cards below show the exact output rules and failure/empty-result behavior of the execution engine.
Parse
The palette-facing unified parser routes to one of the legacy parser engines based on parse_mode.
Configuration Behavior Variables Edge cases
parse_mode: LR / Regex / Json / Css / XPath / Cookie / Lambda Common: input_var (default data.SOURCE), output_var (default PARSED), capture Mode-specific fields: delimiters, regex output format, JSON path, selector/attribute/index, XPath, cookie name, or lambda expression The unified block dispatches to the same engine paths as the legacy parser variants. Only the active mode’s fields determine the extraction. input_var + selected mode → PARSED {output_var} — extracted valueCAPTURE.{output_var} when capture is enabledLegacy ParseLR / ParseRegex / ParseJSON / ParseCSS / ParseXPath / ParseCookie / LambdaParser remain import-compatible. Use data.SOURCE for response namespace input; parsed output is a user variable, not automatically data.{output_var}.
Parse LR
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, left, right, output_var, capture recursive and case_insensitive Non-recursive mode returns the first text between delimiters. Recursive mode collects successive matches and joins them with ", ". "a[one] b[two]" + recursive → "one, two" {output_var} — first extraction or joined recursive resultsCAPTURE.{output_var} when capture is enabledBoth delimiters must be non-empty; the engine rejects empty delimiters to prevent non-advancing recursive parsing. No left/right match writes an empty string in non-recursive mode. case_insensitive affects literal delimiter search.
Parse Regex
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, pattern, output_format (default $1) output_var, capture, multi_line Builds a Rust regex and uses the first capture match. output_format expands capture references such as $1 and $10. pattern /id=(\d+)/ + $1 → PARSED = "42" {output_var} — expanded capture result when matchedCAPTURE.{output_var} when capture is enabledInvalid regex syntax is a block error. No match leaves the existing output variable untouched; configure downstream checks accordingly. multi_line changes ^ and $ behavior.
Parse JSON
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, json_path, output_var, capture Supports RFC 6901 JSON Pointer paths beginning with /. Other paths use JSONPath-lite: dot keys, [n] indexing, wildcards, and simple filters. {"items":[{"id":42}]} + items[0].id → PARSED = "42" {output_var} — stringified scalar/object/array resultCAPTURE.{output_var} when capture is enabledWhitespace-only input deliberately writes an empty output instead of failing. Non-empty invalid JSON is a block error. Missing path resolves to an empty output.
Parse CSS
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, selector, attribute, index, output_var, capture attribute supports text/innerText, innerHTML/html, outerHTML, or a named HTML attribute Parses HTML and selects elements with a CSS selector. index >= 0 selects one element; index = -1 extracts all matches joined with ", ". .price + innerText + index -1 → "10, 20" {output_var} — trimmed selected text, HTML, or attributeCAPTURE.{output_var} when capture is enabledInvalid CSS selector is a block error. No match or an index outside the match set writes an empty output. Any other negative index writes empty; only -1 means all matches.
Parse XPath
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, xpath, output_var, capture Evaluates XPath as string, number, boolean, or node set. Node-set values are joined with ", ". //price/text() → PARSED {output_var} — trimmed XPath valueCAPTURE.{output_var} when capture is enabledInvalid XPath is a block error. If source is not valid XML, the engine retries by wrapping it in a root element. Invalid/unmatched evaluations resolve to an empty output where parsing can continue.
Parse Cookie
Compatibility parser retained for imported configurations. Its input default differs from the other parser variants.
Configuration Behavior Variables Edge cases
input_var (default data.COOKIES), cookie_name, output_var, capture Resolves the cookie collection input and extracts the named cookie value. data.COOKIES + session → PARSED = "…" {output_var} — selected cookie valueCAPTURE.{output_var} when capture is enabledThe default input is the HTTP cookie namespace, not data.SOURCE. A missing named cookie writes an empty output. Use the exact cookie name; do not parse Set-Cookie syntax as an arbitrary response body.
Lambda Parser
Compatibility parser retained for imported configurations.
Configuration Behavior Variables Edge cases
input_var, lambda expression, output_var, capture Applies the retained compatibility lambda-parser behavior to the resolved input. input + lambda_expression → PARSED {output_var} — lambda resultCAPTURE.{output_var} when capture is enabledThis is retained for imported configurations; use the unified Parse block for new parser authoring where possible. Treat expression syntax and result formatting as compatibility-sensitive. 