Custom tools, web chat and MCP

If the app you need isn't listed, you can connect your own systems. These are for teams with a developer.

Custom webhook tools

In Integrations, open Custom webhook tools and create a tool with:

  • a Tool name in lower case with underscores, for example check_order_status,
  • When should the assistant use it?, in plain words,
  • your Endpoint URL, which must be https,
  • What does it do?, from Reads data to Moves money,
  • the parameters the assistant should collect from the caller (text, number or yes/no).

RingMind sends a signed POST request to your endpoint. The page shows the request format and how to check the signature with the tool's signing secret. Your endpoint must reply within 8 seconds; the assistant reads the reply to the caller. Webhook tools can require approval like any integration.

Web chat

On the assistant's page, Turn on web chat to let visitors chat with the assistant on your website, as text, with no phone number needed. It uses the same instructions, knowledge and tools. Publish, then copy the snippet shown into your website.

Web chat tools (Beta) run on your website during a chat, for example opening your contact form. Your site needs a handler for each one.

MCP servers (Beta)

MCP servers gives your assistant selected tools from a Model Context Protocol server. Add the server's https address and list the exact Allowed tools; the assistant can use only those. An optional API key is stored with our voice provider and never shown again.

Web chat tools and MCP tools can't be set to require approval.

Only owners and admins can manage these tools.

Updated 2026-11-04. Still stuck? Contact support from your dashboard.