How do I access deeply nested data from an API response?

Use dot notation with bracket indices in your connection tags. For example, navigates into the data field, then into the results array at index 0, and retrieves the id property.

Data Structure

When you connect blocks, understanding the data structure of different block outputs is important because the output data structure from the source block determines what values are available in the destination block. Each block type produces a specific output structure that you can reference in downstream blocks.

Understanding these data structures is essential for effectively using connection tags and accessing the right data in your workflows.

Block Output Structures

Different block types produce different output structures. Here's what you can expect from each block type:

{
  "content": "The generated text response",
  "model": "gpt-4o",
  "tokens": {
    "input": 120,
    "output": 85,
    "total": 205
  },
  "toolCalls": {
    "list": [],
    "count": 0
  },
  "providerTiming": {
    "duration": 1250,
    "modelTime": 1250,
    "toolsTime": 0,
    "iterations": 1
  },
  "cost": {
    "input": 0.0006,
    "output": 0.001275,
    "total": 0.001875
  }
}

Agent Block Output Fields

content: The main text response generated by the agent
model: The AI model used (e.g., "gpt-4o", "claude-3-opus")
tokens: Token usage statistics
- input: Number of input tokens consumed
- output: Number of output tokens generated
- total: Total tokens used
toolCalls: Object containing the ordered tool-call list and its count
providerTiming: Provider, model, and tool execution timing details
cost: Estimated input, output, tool, and total provider costs

Custom Output Structures

Some blocks may produce custom output structures based on their configuration:

Agent Blocks with Response Format: When using a response format in an Agent block, the defined schema fields are returned at the output root alongside standard execution metadata such as tokens, toolCalls, providerTiming, and cost.
Function Blocks: The result field can contain any data structure returned by your function code.
API Blocks: The data field will contain whatever the API returns, which could be any valid JSON structure.

Always check the actual output structure of your blocks during development to ensure you're referencing the correct fields in your connections.

Nested Data Structures

Many block outputs contain nested data structures. You can access these using dot notation in connection tags:

<blockName.path.to.nested.data>

For example:

<agent1.tokens.total> - Access the total tokens from an Agent block
<api1.data.results[0].id> - Access the ID of the first result from an API response
<function1.result.calculations.total> - Access a nested field in a Function block's result

Common Questions

Without a response format, an Agent block outputs content (the text response), model (the model used, e.g. gpt-4o), tokens (an object with input, output, and total counts), toolCalls (an object with list and count), providerTiming, and cost. There is no separate usage output. When a response format is configured, its fields replace content and model at the output root while the standard execution metadata remains available.

The API block returns data (the response body, which can be any type), status (the HTTP status code as a number), and headers (an object containing the response HTTP headers).

A Function block outputs result (the return value of your function, which can be any type) and stdout (any console output captured during execution).

The Condition block outputs conditionResult (a boolean), selectedPath (with blockId, blockType, and blockTitle of the next block), and selectedOption (the ID of the matched condition). The Router block outputs content (the routing decision text), model, tokens, and selectedPath, but does not include conditionResult or selectedOption.

When you define a response format on an Agent block, the schema fields are returned at the output root instead of content and model. Standard execution metadata such as tokens, toolCalls, providerTiming, and cost remains available.

Use dot notation with bracket indices in your connection tags. For example, <api1.data.results[0].id> navigates into the data field, then into the results array at index 0, and retrieves the id property.