Skip to main content

HTTP Requests Tools

The HTTP Requests tools let your agent call any external API — fetch data, create a record, update something, or delete it. There are four tools, one per HTTP method:

  • Requests Get — read data
  • Requests Post — create data
  • Requests Put — update data
  • Requests Delete — remove data

They all work the same way; the difference is the HTTP verb (and whether they send a body). Pick the one that matches what the API expects.

Tool vs. HTTP node

These tools let an agent decide when and how to call an API during its reasoning. If you instead want a fixed, deterministic API call as a graph step, use the HTTP node.

Adding it to a flow​

In the Tool node's tool picker, choose Requests Get / Post / Put / Delete, then set the URL and (optionally) a schema that tells the agent which parameters it can use.

Inputs​

All four tools share these fields:

ParameterDescriptionRequired
URLThe endpoint to call. Supports variables (e.g. {{$flow.state.customerId}}).Yes
NameThe tool name the agent sees. Defaults to requests_get, requests_post, etc.No
DescriptionTells the agent when to use this tool.No
HeadersJSON of request headers, e.g. an Authorization bearer token.No
Max Output LengthTrims long responses (default 2000). Remove it to return the full response.No

Get and Delete additionally have:

ParameterDescriptionRequired
Query Params SchemaDescribes the available query/path parameters so the agent can figure out which to send.No

Post and Put additionally have:

ParameterDescriptionRequired
BodyA fixed JSON body. If set, it overrides whatever body the agent would generate.No
Body SchemaDescribes the available body fields so the agent can build a valid request.No
Schemas guide the agent

The Query Params Schema and Body Schema don't restrict the URL — they teach the agent what each parameter means so it can fill the right values. Example schema entry:

{
  "limit": {
    "type": "string",
    "in": "query",
    "description": "Limit the number of items to return. ?limit=10"
  }
}

Outputs​

Each tool returns the API's response (trimmed to Max Output Length). It's a single-output tool — the flow continues to the next node. Store the response in flow state or pull a value out of it with the JSON Path Extractor.

Example​

Look up an order by id

  1. Add a Tool node with Requests Get.
  2. Set the URL to https://api.example.com/orders/{id} and add a Query Params Schema describing id.
  3. Add an Authorization header with your API token.

When the agent needs order details, it calls the tool with the right id, and the JSON response comes back for the next step.

Tips​

  • Keep secrets in headers, not the URL. Put API keys in the Headers field.
  • Use variables in the URL to target the right record, e.g. {{$flow.state.customerId}}.
  • Set a Body on Post/Put only when you want a fixed payload — otherwise let the agent build the body from the Body Schema.
  • Raise Max Output Length (or remove it) if the API returns large payloads you need in full.