Agent tools

An agent's tools are what it can do while it talks: look up an order, check a balance, create a ticket. Open the agent and go to Integrations & Tools → Tools. Every tool the agent has is listed there, whatever its kind:

• API call — the agent calls an address of yours with what it learned in the conversation.
• MCP server — the agent uses the tools an MCP server offers: all of them, or only the ones you allow.

Each row shows the tool's name, its kind and one line on what it does, with Edit and Remove. Changes are saved when you press Save tool (or confirm a removal), and the agent uses them from its next conversation.

Add an API call

1. Press Add tool, then API call. The editor opens beside the page.
2. About the tool
   • Name — letters, numbers and underscores, for example check_order_status. The agent sees this name.
   • When to use it — say when the agent should call the tool. This matters most: the agent decides from it.
   • What the agent says while it runs — for example "One moment while I check that." Leave it empty for the default line.
3. Request
   • Method — GET, POST, PUT, PATCH or DELETE.
   • Address — the full https:// address. It can carry an input, like https://api.example.com/orders/%(order_id)s.
   • Authorization header — sent as the Authorization header, for example Bearer …. Optional.
   • Other headers — a JSON object. Optional.
4. Inputs the agent gathers — one row per value the agent must learn before calling: its name, type (string, number, integer or true/false), what it is, and whether it is required. The agent keeps asking until it has every required input.
5. Request values — what the request carries: the body, or the query for GET. Write %(name)s where an input goes (%(name)i for a whole number, %(name)f for a decimal). Fill from inputs adds one for each input.
6. Press Save tool. If something is missing, the editor says what, in plain words, and nothing is saved.

The definition view

Press Definition (JSON) to see the whole tool as one JSON object, or paste one in and press Use this definition to fill the fields:

{
  "name": "check_order_status",
  "description": "Use when the caller asks where their order is.",
  "pre_call_message": "One moment while I check that.",
  "parameters": {
    "type": "object",
    "properties": {
      "order_id": { "type": "string", "description": "The caller's order number" }
    },
    "required": ["order_id"]
  },
  "key": "custom_task",
  "value": {
    "method": "GET",
    "url": "https://api.example.com/orders/%(order_id)s",
    "param": { "order_id": "%(order_id)s" },
    "api_token": "Bearer YOUR_TOKEN",
    "headers": {}
  }
}

An agent that speaks two or more languages can say a different line in each while a tool runs: edit pre_call_message in the definition view as an object keyed by language code.

Add an MCP server

1. Press Add tool, then MCP server.
2. Server
   • Name — a short name, for example crm. Names are unique on an agent, and capitals don't count.
   • Server address — the server's https:// address. It must be reachable on the public internet.
   • Connection — Streamable HTTP (most servers) or server-sent events (older servers).
   • What it's for — optional; shown in your tools list.
3. Sign-in — None, a bearer token, or an API key, with the token or key.
4. Allowed tools — the names of the server's tools the agent may use, one per line. Leave it empty to allow every tool the server offers.
5. Press Save tool.

Flow agents

A flow agent's tools are set in the flow builder's Tools tab, with the same list, Add tool and editors as above. Integrations & Tools on a flow agent opens it there.

• Under each API call, choose where it is offered: Every step, or Chosen steps and the steps you pick. That choice is part of the flow, saved with the builder's Save.
• A tool itself saves on its own. Save or discard the flow's other changes first; until then Add tool, Edit and Remove wait, and say why.
• Add call transfer opens the editor on the platform's call transfer tool, ready to save.