Skip to main content

​
Overview

The Web Tool Node lets you use Web Tools within a flow agent, with structured control over how the tool’s response is handled. You can extract specific values from the response, use them in variables, and route the conversation based on the results.
For a full explanation of what web tools are, how to register them, and code examples, see the Web Tools documentation. This page covers the flow-specific aspects of using them in nodes.

​
Adding a Web Tool Node

  1. Open your Flow Agent
  2. Click Add Node and select Web Tool Node
  3. Configure the node to reference a registered web tool
  4. Add transitions based on the tool’s response

​
Extracting Data from Responses

The key advantage of using web tools in a flow agent (vs. a single prompt agent) is output mapping. You can extract specific values from a web tool’s JSON response and store them in variables for use later in the flow. 
Web Tool Node: Check_Cart
  Output Mapping:
    cart_total: $.total
    item_count: $.items.length
  ↓ (Equation: {{cart_total}} > 100)
Conversation Node: "Your cart total is {{cart_total}}. Would you like to checkout?"
  ↓ (Equation: {{cart_total}} <= 100)
Conversation Node: "You have {{item_count}} items. Can I help you find anything else?"
In a single prompt agent, the web tool’s response goes directly to the LLM without extraction. In a flow agent, you control exactly which values are extracted and how they’re used.

​
Transitions

Web Tool Nodes support all transition types:
  • Always: Proceed to the next node regardless of response
  • Natural Language: Route based on the meaning of the response
  • Equation: Route based on extracted values from the response

​
Processing Message

Configure a message the agent speaks while the web tool executes:
  • Static: "One moment while I look that up..."
  • Prompt-based: "Let me find the {{product_category}} for you..."

Web Tools

Full web tools documentation with SDK registration and examples

Tool Node

Server-side tool execution for API calls

Variables

Use extracted tool data in your flow

Transitions

Route based on tool responses