Pattern
Parse value discipline
Tool, connector, and HTTP results that reach users as raw JSON or break silently after an upstream API change.
Last reviewed 8 July 2026
The pattern
After every tool, connector, or HTTP action, add a Parse value node. Results from these actions arrive as plain text or untyped values, not as usable fields. Give the node a sample of the real response and let it derive the schema. The derived schema is frozen: it does not update itself when the API behind it changes. When the upstream API changes, pull a fresh sample and derive the schema again.
When to use it
- After every tool, connector, or HTTP request action in a topic.
- After every agent flow that returns a structured result as a string.
- Whenever the chat shows raw JSON instead of a readable answer.
- Whenever parsing broke without any change on your side; check the upstream API first.
Steps
- Run the tool, connector, or HTTP action once and copy a real sample response.
- Add a "Parse value" node directly after the action.
- Set it to work from sample data, using "Get schema from sample JSON".
- Paste the sample and confirm the derived schema.
- Store the parsed fields in variables and use only these fields in later nodes.
- Note which API version the sample came from.
- When the upstream API changes, repeat steps 1 to 4 with a fresh sample.