Tools & Tools Log Documentation
The Tools section enables AI agents to connect with external services, automate workflows, trigger APIs, manage bookings, send messages, and integrate with third-party platforms.
The My Tools area is divided into three tabs — API/Webhook, Additional Tools, and MCP Tools — each serving a distinct integration purpose.
| tab | description |
|---|---|
| API/Webhook | Create custom API/Webhook tools to connect external services. |
| Additional Tools | Pre-built communication and CRM tools for agents. |
| MCP Tools | Connect to 28+ third-party platforms like Gmail, Zoom, Razorpay. |
API / Webhook Tools
API/Webhook tools allow AI agents to connect with external APIs and services using HTTP methods such as GET, POST, PUT, DELETE, and PATCH. These tools enable real-time integrations, backend operations, and workflow automation.
- Connect external APIs and services
- Fetch real-time data
- Perform backend operations
- Trigger external services
- Automate workflows and processes
1.1 Creating a New API/Webhook Tool
Navigate to Tools → API/Webhooks and click Create New Tool. The creation panel opens with multiple configuration tabs.
The Basic tab contains the core configuration fields:
| field | details |
|---|---|
| Tool Name * | Required. Unique name for the tool. |
| Description | LLM instructions — describe when this tool should be called and how to use parameters with examples. |
| Method | HTTP method — GET, POST, PUT, DELETE, PATCH. |
| URL * | API endpoint URL (e.g. https://api.example.com/endpoint/{id}). |
| Import cURL | Paste a cURL command to auto-fill fields. |
| Export cURL | Export current configuration as cURL. |
| Preview Request | Test the request before saving. |
Available configuration tabs when creating a tool:
| tab | description |
|---|---|
| Basic | Tool name, description, HTTP method, endpoint URL. |
| Headers | Add custom HTTP headers (e.g. Authorization, Content-Type). |
| Query Params | Add URL query parameters. |
| Path Params | Define path parameters if required. |
| Body | Configure request body for POST, PUT, or PATCH. Constant default values are stored as the selected data type (boolean, number, integer), not as strings. |
| Auth | Set up authentication — Bearer Token or Basic Auth. |
| Settings | Timeout, execution mode, response handling, category. |
On the Body tab, each JSON parameter has a data type and a value type. When Value Type is Constant, the Default Value field matches the data type and is saved in that native type — not as a quoted string.
| field | details |
|---|---|
| Body Type | None, JSON, Form Data, or Raw. |
| Data Type | String, Number, Integer, Boolean, Object, or Array. The Default Value field matches this type and rejects values that do not match (for example letters in an Integer). |
| Value Type | LLM (AI fills it), Constant (fixed native-typed value), or Dynamic (runtime variable). |
| Default Value | For Constant: Boolean shows true/false (defaults to false, stored as false not "false"). Number and Integer use numeric inputs and are stored as numbers. Strings stay strings. |
1.2 Tool Settings
Click the Settings tab within the tool creation panel to configure advanced behavior such as timeout duration, execution mode, and response handling.
| field | details |
|---|---|
| Timeout (seconds) | Default 30 seconds. Max wait time for API response. |
| Execution Mode | Synchronous (default) — waits for response before continuing. |
| Allow Scheduling | Disabled for sync tools — sync tools cannot be scheduled. |
| Response Handling | Auto – Smart extraction (saves tokens) — extracts key data automatically. |
| Request Format | Auto — platform selects the best format. |
| Category | General (default) — organizes tools by type. |
Steps to create and save a tool:
- Navigate to Tools → API/Webhooks and click Create New Tool.
- Enter the Tool Name and Description in the Basic tab.
- Select the required HTTP Method such as GET, POST, PUT, or DELETE.
- Enter the API endpoint URL.
- Use Import cURL, Export cURL, or Preview Request if required.
- Configure Headers such as API Keys, Tokens, or Content-Type.
- Add Query Parameters and Path Parameters if needed.
- Configure the request body for POST, PUT, or PATCH. For Constant parameters, pick Boolean/Number/Integer so Default Value is stored as
falseor42, not"false"or"42". - Set up Authentication such as Bearer Token or Basic Auth.
- Configure advanced Settings such as Timeout, Execution Mode, and Response Handling.
- Click Create Tool to save and create the API/Webhook tool.
Additional Tools
Additional Tools are pre-built communication and CRM utilities that help AI agents perform common business operations without requiring complex configuration.
Communication Tools
| tool | description | status |
|---|---|---|
| WhatsApp Template | Send approved WhatsApp message templates. | Available |
| SMS OTP | Verify user phone numbers via SMS OTP. | Available |
| SMS | Send SMS messages to customers. | Coming Soon |
| RCS Template | Send rich RCS message templates. | Coming Soon |
| Voice Call | Initiate voice calls to customers. | Coming Soon |
CRM Lead & Booking Tools
Give your AI agent the ability to create leads, manage bookings, and check availability directly from a conversation.
| tool | description |
|---|---|
| Create Lead | Capture a new lead from AI conversation. |
| Create Booking | Schedule an appointment for a customer. |
| Get Available Slots | Check open time slots for a given date. |
| Get Services | List all services with pricing and duration. |
| Check Booking | Look up booking status by number or phone. |
| Cancel Booking | Cancel an existing appointment. |
Key capabilities of Additional Tools:
- WhatsApp Template Messaging
- SMS OTP Verification
- Booking Management
- Lead Creation
- Service and Slot Management
- Customer Workflow Automation
MCP Tools (Platform Integrations)
MCP Tools allow AI agents to connect with third-party platforms such as Gmail, Zoom, Razorpay, and Resend. These integrations extend the capabilities of the agent and enable platform-specific operations.
- Connect external platforms
- Enable cross-platform workflows
- Perform platform-specific operations
- Automate communication and payment systems
Popular platforms available in the catalog:
| platform | auth | category | tools |
|---|---|---|---|
| Gmail | OAuth 2.0 | Email, Communication, Productivity | 1 tool |
| Zoom Meetings | OAuth 2.0 | Video, Meetings | 13 tools |
| Razorpay | API Key | Payments, Collections, Fintech | 24 tools |
| Resend | API Key | Email, Communication, Marketing | 2 tools |
3.1 Connecting to a Platform (e.g. Gmail)
Each MCP platform requires OAuth 2.0 or API Key authentication. The following steps demonstrate connecting Gmail:
- Navigate to MCP Tools and select Gmail.
- Click Connect to start the integration process.
- Create or select a project in Google Cloud Console.
- Enable the Gmail API.
- Create OAuth 2.0 Client Credentials.
- Add the authorized redirect URI:
https://app.fonada.ai/functions/v1/mcp_oauth_callback - Copy Client ID and Client Secret.
- Add the authorized redirect URI.
- Click Authorize with Gmail to complete the setup.
Connecting Tools to an Agent
After configuring tools successfully, they can be attached to AI agents from the Agent Configuration panel.
- Navigate to Create Agent or Edit Agent.
- Open the Tools & Events tab.
- Select or deselect tools based on requirements.
- Save or update the agent configuration.
Tool Log
The Tool Log section provides complete visibility into all tool executions performed by AI agents. It helps monitor execution status, debug issues, and analyze agent interactions.
- View tool executions and current state
- Track failed executions
- Monitor execution timestamps
- Inspect user inputs and tool arguments
- Review tool responses and outputs
- Export logs in JSON format
Conclusion
The Tools ecosystem enhances AI agents by enabling integrations, workflow automation, communication systems, CRM operations, and platform connectivity. Combined with Tool Logs, these capabilities provide powerful monitoring, debugging, and operational visibility.