Tool builder is the page where you design, test, and manage a tool: the Tools page lists every tool in your account, and opening a tool shows the canvas with its input, logic steps, and output. This reference names every page, tab, menu, and canvas element you'll meet while working with tools, with a link to the procedure that uses each one. It's for integrator.io users at any level; if you're building your first tool, start with Create a tool.
Open the Tools page
Go to AI studio, and then select Tools. Every procedure in this set starts here. Select a tool's name to open it in Tool builder.
Tools page
The Tools page lists every tool in the current environment. Use Search to filter by name, and + Create tool to start a new one.
| Column | Description |
|---|---|
| Name/Description | The tool's name. Select it to open the tool. Select Description to read or edit the description. |
| Integration | The integration the tool belongs to. Select it to open the integration. |
| Last updated | When the tool was last saved. |
| Actions | The actions menu for the tool. Some rows show Expired instead — see Expired tools. |
Actions on the Tools page
Select Actions in a tool's row.
| Action | Description |
|---|---|
| Edit tool | Opens the tool in Tool builder. Selecting the tool's name does the same. |
| View audit log | Opens the tool's Audit log tab. |
| Used by | Lists every flow, API, AI agent, MCP server, and tool that references this tool. Check it before you change or delete a shared tool. |
| Download tool | Downloads the tool as a zip file. See Download and upload a tool. |
| Clone tool | Copies the tool, with its nested tools and steps. See Clone a tool. |
| Move to integration | Moves the tool to another integration. See Move a tool to another integration. |
| Delete tool | Moves the tool to the recycle bin. See Delete a tool. |
Users with Monitor access see the menu but can't edit, move, or delete tools.
Expired tools
Some rows show Expired in place of the Actions menu, and the tool can’t be opened, cloned, moved, or deleted from the list. A tool created as a draft through the REST API expires if it isn’t saved within 48 hours, and an expired draft can’t be restored from the recycle bin; recreate it instead.
Tool builder header
The header shows the tool's name, Last saved with the time of the last save, and three controls.
| Control | Description |
|---|---|
| Tool name | Hover over the name and select Edit to rename the tool in place. |
| Run test | Runs the tool with its mock input and opens the Run console. Disabled until both the tool input and tool output are configured. See Test a tool in Tool builder. |
| Settings | Opens Tool settings: Name (required), Description, and Integration name (read-only). |
| Actions | Used by, Download tool, Clone tool, and Delete tool — the same actions as on the Tools page, without Edit tool, View audit log, and Move to integration. |
There is no publish step. Changes are saved as you make them, and callers use the saved tool.
Tabs
| Tab | Description |
|---|---|
| Build | The canvas, described below. |
| Logs | Invocations of the tool by AI agents, MCP servers, and REST API callers. See View tool invocation logs. |
| Connections | The connections the tool's steps use, with Name, Status, Application, API, Last updated, Queue size, and Actions. Select a connection's name to edit it. |
| Audit log | Every change to the tool and its steps, filtered by date range (default Last 1 year), with Time, User, Source (UI or System), Resource type, Resource name, Action, Field, Old value, and New value. Select Download to export the log. Lookups and imports inside a tool appear with the resource type Export or Import. |
Canvas
The Build tab shows the tool as a left-to-right sequence. Select a step to open its editor.
| Element | Description |
|---|---|
| Tool input | The first step. Defines the input schema, mock input, and trace key template. A new tool's input step is named input until you rename it. See Configure tool input. |
| Tool output | The last step. Defines the output schema and the mapping into it. A new tool's output step is named output until you rename it. See Configure tool output. |
| Logic steps | Lookups, imports, nested tools, AI agents, and guardrails between the input and output. The step type (for example, Lookup) and the application's logo appear on the step. |
| Configure | Appears on a step that isn't configured. Select it to open the step's editor. |
| Add step | The + between steps. Opens the step picker, described below. |
| Router | The diamond between steps when the tool has branching. Each dotted line from it is a branch, labeled with the branch name (default for a tool with one branch). See Add branching to a tool. |
| Configured-step chips | Small icons below or after a step showing what's configured on it — a transformation after Tool input, a mapping after a lookup or below Tool output. Select a chip to open that editor. |
| View controls | Four controls in the lower-left corner: Zoom in, Zoom out, Zoom to fit, and Show map. |
Step picker
Select Add step between two steps.
| Option | Description |
|---|---|
| Add destination / lookup | Adds a lookup (read) or an import (write, update, or delete) to an application. See Add lookups and imports to a tool. |
| Add AI agent | Adds an AI agent as a step. See Create an AI agent. |
| Add tool | Adds another tool as a nested step. See Use a tool in flows, APIs, AI agents, and MCP servers. |
| Add guardrail | Adds a guardrail that checks each record against a policy. See Create a guardrail. |
| Add branching | Routes records to different steps by condition. See Add branching to a tool. |
Step menus
Each step has More at its upper-right corner. The items depend on the step type.
| Step | Items |
|---|---|
| Tool input | Transformation — Restructure the input before the next step; available once the tool input is configured. See Configure tool input. |
| Lookup or import | Under Incoming data: Input filter and Mapping. Under Outgoing data: Transformation, Output filter, Pre save page hook, Results mapping, Post response map hook, and Error handling (lookup; an import shows its own hooks and response mapping). Then Clone and Remove. See Add lookups and imports to a tool. |
| Tool output | Pre map hook, Mapping, and Post map hook, in the order they run. See Configure tool output and Map data in a tool. |
Run console
Selecting Run test opens the Run console at the bottom of the canvas, with one row per test run that you can expand to one row per step. Steps that ran show a blue T. See Test a tool in Tool builder for the columns and how to read errors.