Tools: connecting the agent to your own systems

What a tool is for

A tool is an HTTPS address that runs on your system (an API endpoint). The agent calls it when needed during a conversation: for example to read appointment availability, shipping status or a customer's balance from your system.

Use a tool for any system that has no ready-made integration. Open “Tools” from the menu; adding, editing, deleting and testing tools require the owner or admin role.

Adding a new tool

1. Press “New tool”.
2. Write the “Tool name” in lowercase with underscores, for example check_availability.
3. Under “When should it be used?”, describe clearly what the tool does and for which questions it should be called. The agent decides when to call the tool from this description.
4. Enter the method (GET or POST) and the address. The address must start with https; local and private network addresses are rejected.
5. Use “Add field” to define the fields the tool expects: name, type, description and whether it's required. The agent fills these fields from the conversation. Types are explained below.
6. Choose the “Authentication”: none, Bearer token or a custom header (with its header name). The secret is stored on the server and never shown again; leave it blank when editing to keep the saved value.
7. Before saving, try it with sample values using “Test call”; you see the response or the error right away.

Field types and nested fields

Every field has a type, and the value is sent to your endpoint in that type. For example, a “Yes/No” field is sent as true, not as the text "true", and a “Number” field typed as 1,234.5 is sent as 1234.5.

• Text, Number, Yes/No: a single value. A Yes/No field understands yes, no, true, false, 1 and 0.
• Date: you can write 06.10.2026 (day first) or 2026-10-06; it's sent as 2026-10-06. Date and time: for example 06.10.2026 14:30; it's sent as 2026-10-06T14:30:00.
• Object: a group with its own sub-fields, for example a customer (name, email). If you add no sub-fields, the value is sent as is, as free-form JSON.
• List: several values. Choose the “Item type”; if the item is an Object, define the item's fields, for example order lines (product ID, quantity).

Fields can be nested up to 5 levels deep. Object and List can only be chosen for POST tools; a GET request can't carry nested data.

On POST tools an “Example body” appears below the fields: the shape of the JSON body your endpoint will receive. You can compare it with what your endpoint expects. In the “Test call”, each field comes with an input that suits its type; Object and List fields open pre-filled with the example body.

If a value doesn't match its field's type (for example “many” in a Number field) or a required field is empty, the request isn't sent; the error says which field it is, for example items[1].id (the id field of the second item).

Tools that change data

If the tool changes something in your system (creating a record, a cancellation and so on), check “This tool changes data”. Such tools are never retried with different values, and every call is logged. They appear in the list with a “Changes data” badge.

Using a tool in an agent

• On the AI Assistant step's “Tools” tab, choose which tools the agent can reach: all of them (including ones added later) or the ones you select.
• A “Selection” step can load its options from a tool; for example free appointment slots are listed as cards.
• A “Tool Call” step calls the tool at a specific point in the flow, without AI, and saves the answer to a variable.

See the AI Assistant step, Selection step and Tool Call step articles.

Managing the list

Search tools by name or description, and filter by method and authentication type. Tools that are failing are marked with a “Failing” badge. When you delete a tool, the agent stops calling it.