HTTP tools
An HTTP tool calls an external API. You build the request in the HTTP API Builder — a Postman-style editor — on the Implementation step of the Create a tool wizard, after choosing the HTTP API target.
Click Fullscreen on the Implementation step to open the full HTTP API Builder with a side reference panel. Press Esc or click Done Editing to return.
The request bar
At the top you choose the method and enter the URL.
- Method —
GET,POST,PUT,PATCH, orDELETE. - URL — enter an endpoint, or paste a full cURL command and the builder parses it into method, URL, headers, and body (you’ll see a cURL parsed badge). Type
{{in the URL to insert an input or config variable. - Send — runs the request and shows the response below.
Headers, Params, Body, Auth
The request is organized into four tabs. Each tab badges how much is configured.
Headers and Params
Add key/value rows. Headers use Header name / Header value; query params use Parameter / Value. Values accept {{...}} variables.
Body
Set the Body Type:
| Type | Use |
|---|---|
| None | No request body. |
| JSON | A JSON payload (the editor pre-fills { "key": "value" }). |
| Form | Form-encoded fields. |
| Raw | A raw string body. |
Auth
Pick an auth type and fill its fields:
| Auth type | Fields |
|---|---|
| No Auth | — |
| Bearer Token | Token |
| API Key | Header Name (default X-API-Key) and API Key Value |
| Basic Auth | Username and Password |
| OAuth2 Client Credentials | Token URL, Client ID, Client Secret, and optional Scope |
OAuth2 Client Credentials automatically fetches an access token before each request. The Token URL must be the authorization server’s token endpoint.
Keep secrets out of the tool — map to config
Never paste a raw API key into the builder. Instead, click Map to Project Configs and replace sensitive fields with project config references. As the builder notes: “This keeps secrets out of the tool definition.”
The mapper lists every mappable field — Bearer Token, API Key, Basic Auth Username/Password, OAuth2 credentials, and individual headers — and lets you point each at a project config with Select config….
Any {{config.xxx}} you use is auto-detected and required as a project secret. See Configuration & secrets.
Send a test request
Click Send to run the request against the live endpoint. The Response section shows:
- Status and status text, plus request duration and body size.
- The Resolved URL with variables substituted.
- Template Resolutions — how each
{{...}}resolved. Anything that couldn’t resolve appears as[UNRESOLVED…]in red. - Headers and the Body (with Pretty / Raw views).
A test Send hits the real endpoint. For an Action tool (side effects), test against a safe or staging endpoint.
Common issues
[UNRESOLVED…]in the response — a{{input.xxx}}or{{config.xxx}}reference has no value. Provide a test input, or add the config under Configuration → Integrations.- 401 / 403 — check the Auth tab and that mapped config values exist and are correct.
- Secret shows in the definition — use Map to Project Configs rather than pasting the raw value.