NovalinkIn dev

Use case

Web research agent with an API tool

Updated September 17, 2026

Some questions need live data. Instead of hard-coding the calls, attach an HTTP Request node to an agent as a tool. The agent decides when to call it, with which arguments, and how many times.

Nodes used:manual_triggeragenthttp_requestoutput

How the workflow runs

  1. The trigger carries a research question.
  2. The research agent has one tool: an HTTP Request node connected to its tools port with a dashed tool edge.
  3. The agent calls the tool as often as it needs, up to its max tool rounds (6 by default), then writes the summary.
  4. The Output node marks the summary as the workflow result.

Describe the tool

The tool node's description and argument schema are what the model sees. Reference the arguments in the URL with {{ args.<field> }}.

Search · HTTP Request
URL: https://api.example.com/search?q={{ args.query }}

Tool description:
Search articles. Call once per distinct query.

Tool arguments (JSON Schema):
{
  "type": "object",
  "properties": { "query": { "type": "string" } },
  "required": ["query"]
}

When a call fails

A failing tool does not fail the run. The agent receives an error result and can retry with different arguments or explain what it could not find. Every call and response is recorded on the run for replay.

Keep it bounded

Build it on the canvas

Create a free account and run your first workflow in the browser, or run Novalink on your own machine.