Documentation
Extending bot capabilities with external integrations.
Tools let your bot take actions beyond generating text — sending media, searching your knowledge, managing contacts, escalating to a human, calling your APIs, and more. There are two kinds: built-in tools that ship with every bot and just need switching on, and custom tools you configure to reach your own systems. When the AI decides it needs a tool, it fills in the required parameters and Neuron executes the call.
Every bot comes with a library of ready-made tools — no setup, just switch them on. They are grouped by purpose: utilities (date & time, calculator, web search, fetch a URL, QR codes, short links, weather), WhatsApp actions (send image/document/sticker/voice note, react, group info, post to a WhatsApp Channel or Status), contacts & lists (look up, save, and segment contacts, remember preferences), knowledge (search the knowledge base, read text from an image), reminders & scheduled tasks, engagement (polls), escalation (hand off or ask your team), translation, and advanced actions (make an HTTP request, run sandboxed JavaScript). Toggle them per bot in the bot's "Built-in Tools" tab.
Most tools are on by default; a few sensitive ones — deleting messages, posting to a Channel or Status, creating scheduled tasks, and running code — start off until you enable them. Tools that only make sense in a group (like listing group participants) are hidden automatically in direct-message chats.
The "Create Scheduled Task" built-in tool lets a bot schedule autonomous follow-ups for itself — for example, "check back in 3 days" or a recurring daily summary. It supports one-off, recurring (cron), and interval schedules. It is off by default; enable it in the Built-in Tools tab. You can also create and manage a bot's scheduled tasks directly from its Tasks tab, where each run is logged with its result.
Three built-in tools cover human-in-the-loop moments: Escalate hands the conversation to a person and pauses the bot until someone takes over; Notify Team alerts your internal team of an enquiry while the bot keeps chatting; and Request Guidance asks your team a quick question without escalating. These pair with the Conversations takeover flow and the platform Approvals system.
When you need your bot to reach your own systems, add a custom tool from the bot's "Tools" tab. There are three types — HTTP API, webhook, and MCP — and each defines a parameters schema so the AI knows what arguments to supply.
The most common tool type. Configure an endpoint URL, HTTP method, headers, and body template. Define a parameters schema so the AI knows what arguments to provide. The bot will call the API and use the response in its reply.
Example: Weather API tool
{
"name": "get_weather",
"description": "Get current weather for a city",
"type": "http_api",
"config": {
"url": "https://api.weather.com/current",
"method": "GET"
},
"parametersSchema": {
"type": "object",
"properties": {
"city": { "type": "string", "description": "City name" }
},
"required": ["city"]
}
}Webhook tools receive data from external services. When you create a webhook tool, Neuron generates a unique URL. External services POST data to this URL, and the bot can process and respond to it.
MCP (Model Context Protocol) tools connect to external MCP servers. Provide the server URL and Neuron will discover available tools automatically. This is useful for connecting to complex services that expose multiple capabilities.
Tools support multiple auth types: none (public APIs), api_key (key in header or query), bearer (Bearer token), basic (username/password), and oauth2 (OAuth 2.0 flow). Configure auth when creating or editing a tool.
Store sensitive values like API keys as secrets. Secrets are encrypted at rest and can be referenced in tool configurations. Add secrets from the tool's detail page.
Secrets are write-only — once saved, you cannot view the original value. You can only replace or delete them.
Before deploying, test your tools from the tool detail page. Provide sample arguments and Neuron will execute the tool and show you the response. This helps catch configuration errors early.