Skip to main content

Data Flow Spy Node

The Data Flow Spy Node lets you inspect, debug, and visualize the data flowing through your workflow at any point. It displays the incoming data in a readable Markdown format, making it easy to understand and troubleshoot your workflow.

Display Data Flow Spy Node

Supported Data Formats

The Data Flow Spy Node accepts any data type:

  • Strings: Displayed as plain text or Markdown.
  • Numbers: Displayed as-is.
  • Objects/Arrays: Rendered as formatted JSON blocks.
  • Markdown: Rendered with full Markdown support (headings, lists, code, etc).

Example Usage

For example usage, see the Current Time workflow or Weather Dashboard workflow, which demonstrate using Data Flow Spy nodes to inspect intermediate results.

Common Use Cases

  1. Debugging: Inspect the output of any node in your workflow.
  2. Data Inspection: View raw or formatted data at any stage.
  3. Markdown Preview: Render Markdown output from LLMs or other nodes.
  4. Error Tracing: Quickly spot issues in data transformations.
  5. Workflow Development: Rapidly iterate by checking intermediate results.

Best Practices

  • Place after key nodes: Add Data Flow Spy nodes after important processing steps to verify outputs.
  • Use for troubleshooting: Temporarily insert to debug unexpected results.
  • Preview Markdown: Use to check LLM-generated Markdown or JSON.
  • Remove for production: Remove or disable unnecessary spies in finalized workflows for clarity.

Troubleshooting

Common Issues

  • Large data freezes UI: Very large JSON or text may take time to render. The node shows a loading spinner for large content.
  • Unreadable output: Non-JSON objects are rendered as best-effort Markdown or code blocks.
  • Markdown not rendered: Ensure your data is a valid Markdown string or JSON.

Supported Data Types

  • String (including Markdown)
  • Number
  • Boolean
  • Object (including arrays)
  • Null / Undefined

Performance Tips

  • Avoid sending extremely large data blobs for inspection.
  • Use JSON Reformatter nodes to trim or format data before spying.
  • For large arrays/objects, consider inspecting only a subset.