Custom HTTP

Define account-level HTTP actions with methods, auth, bodies, and your own backends.

Setup

Open Settings → Actions and open Custom HTTP.
Create connection to your base URL and default auth if you use one connection for many calls, or attach auth per action where the product allows.
Define actions with the following details.
- HTTP method, path, query, and headers
- Body (none, JSON, form-encoded, or raw)
- Authentication (none, API key in header or query, Bearer, Basic, or custom header)
- Timeouts and optional test requests against your endpoint
Name and describe each action clearly; agents see these when enabling tools under Agents → Actions.

There is no fixed list of Custom HTTP actions. The capabilities are entirely what you define.

You define the actions (keys, parameters, and descriptions). The platform executes the HTTP call and exposes the tool to agents that enable it.

Treat Custom HTTP as production traffic. Validate payloads, authenticate callers, and rate-limit sensitive operations on your API.