Custom Tools

The workspace's own HTTP tools, the ones an agent can call mid-conversation. Define the request, map the response, store the secret safely — and test against the stored tool before an agent ever runs it.

At a glance

  • Method, URL, headers and timeout per tool
  • An input-schema builder and a response mapping
  • Secrets write-only — saved values never shown
  • A last-run badge with outcome and status code
Custom Tools

The tool list

One panel: each row shows the name, the truncated method and URL, a last-run badge — outcome and status code, with how long ago — and an on/off badge beside Edit. New Tool starts a fresh one.

The editor

Name, Key and Description, then the request: a method select, the URL, a timeout of 2, 5, 8 or 10 seconds, header rows and auth — none, bearer, or a named header. The input-schema builder and the response mapping shape what goes in and what comes back, and an Enabled switch decides whether agents may call it.

Secrets and the test panel

The secret box is write-only: an empty box beside "saved" means the stored value is kept, never that it is gone. The test panel takes sample input and Run, then lays the raw request and response side by side — and it runs against the stored tool, so save first.

  1. Define the callName and key the tool, pick the method — GET, POST, PUT or PATCH — then set the URL and a timeout of 2, 5, 8 or 10 seconds.
  2. Shape input and outputThe input-schema builder takes name, type, description and Required per field; response mapping pairs each field with a dot path.
  3. Save, then testTest runs against the stored tool, so a new tool saves first. Sample input in, Run, and the raw request and response sit side by side.