Aller au contenu principal

Tool Executor

Category: Agent
Node id: tool-executor

Executes registered tools/functions on behalf of agents via HTTP or builtin handlers

What it does​

  • HTTP-based external tool invocation with auth support
  • Built-in tool library (get_current_time, calculate, format_json)
  • Tool call ID tracking for agent loop integration
  • Graceful error handling with status reporting
  • Configurable tool registry with per-tool endpoint and auth

Use cases​

  • Executing tool calls from agent reasoning loops
  • Integrating external APIs as tools in agentic workflows
  • Running built-in utility functions within pipelines

Runtime​

  • Performance tier: variable

Input ports​

NameTypeRequiredDescription
tool_nametextYesName of the tool to execute
tool_argsjsonNoArguments to pass to the tool
tool_call_idtextNoTool call ID for tracking

Output ports​

NameTypeRequiredDescription
tool_nametextNoName of the executed tool
tool_call_idtextNoTool call ID
resultanyNoTool execution result
statustextNoExecution status (success or error)
http_statusnumberNoHTTP status code (for HTTP tools)
errortextNoError message if execution failed

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Execution Modeexecution_modeenumNohttphttp, builtinHow to execute the tool
Tool Registrytool_registryjsonNoRegistry of tool configurations (endpoint, method, auth_token per tool)

Errors​

CodeDescription
TOOL_NAME_REQUIREDNo tool_name input was provided
TOOL_NOT_FOUNDTool name not found in the configured registry
ENDPOINT_MISSINGNo endpoint configured for the requested tool
UNSUPPORTED_MODEexecution_mode must be http or builtin

Runtime notes​

  • On HTTP tool failure, returns status='error' with the error message instead of failing the node
  • http_status output is only present for HTTP execution mode, not builtin tools
  • Builtin tools: get_current_time, calculate, format_json — unknown builtins return status='error'
  • tool_registry config maps tool names to {endpoint, method, auth_token} for HTTP mode

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.