Bring your own tools
Your receptionist isn't limited to the apps on Digui's list. Connect your booking system, CRM or store through its API or MCP server, and your receptionist uses it on calls and in your website chat: it sees free times, books and looks up orders. Every plan has tools, Free included.
Build Yours FreeWhich way fits your system?
| Your system has | Connect it with | What your receptionist does |
|---|---|---|
| An API | API Request | Reads from your system and changes things in it, one request per tool |
| An MCP server | MCP Server | Uses the server's tools when a caller needs them |
| Make, n8n, Zapier or your own server | Webhook | Sends every call and chat there once it ends |
| None of these | Bring Your Own Tool or API | Tell us what it should do, and we build it for you |
How do you connect your API?
Each request is its own tool, like one to see free times and one to book. It works with an API that takes a key, a username and password, or nothing (not a sign-in with Google or another account). In Tools:
- Press New Tool and pick API Request.
- Paste your API's documentation for one request, a cURL example or a description, and press Make the cURL.
- Check the request and who fills each value, then type your key.
- Press Test, and give it to your receptionists. It saves as you go.
Can you see what it sends?
Yes. Each request is a cURL you can read and edit, sent exactly as written and only to its address, and your key stays encrypted. Before your receptionist changes anything, like booking an appointment, it says what it's about to do and waits for a yes (more).
How do you connect an MCP server?
Your receptionist uses its tools as they are. In Tools:
- Press New Tool and pick MCP Server.
- Type its address (https, Streamable HTTP) and its token, if it asks for one.
- Digui checks it can reach it and lists its tools, so you see exactly what it can use.
- Write when to use it, and give it to your receptionists (more).
How does it know who's calling?
By the number they call from, once one of your tools can look them up by it. Who the person is comes from the phone line, or your website's signature in the chat, never from what they say. It can look them up as each call or chat starts, so it already knows who it's talking to (how).
Can your other systems hear about every call?
Yes, with a webhook. After every call and chat, Digui posts it as JSON to the address you give: an AI summary, the details you ask for (like the customer's name) and the transcript. Each request is signed, so your server can check it came from Digui (how).
What if your app has no API you can use?
At the bottom of Tools, use Bring Your Own Tool or API to tell us what your receptionists should do with your CRM, booking system or store, and we'll build it (more). For apps already there, like Google Calendar, Shopify or HubSpot, see the full list.
Last updated:
Build Yours Free