01 / API
Native API
Point the agent at your API — OAuth and JWT built in. It reads, writes, and chains calls in real time during the conversation.
Best when: the system has a documented API and you want millisecond latency.
Integrations · Shipped today, the rest one webhook away
Connect a calendar, a webhook, or any REST API — the agent books, looks up, and sends, right on the call. Everything else is one webhook away through n8n, Make or Zapier.
How it connects
The agent isn't fussy about the integration shape. Some systems give us a clean API. Some prefer webhooks. Some you stitch together in an iPaaS. The newest ones speak MCP. We meet each one where it lives.
01 / API
Point the agent at your API — OAuth and JWT built in. It reads, writes, and chains calls in real time during the conversation.
Best when: the system has a documented API and you want millisecond latency.
02 / Webhook
The agent fires a signed webhook on every event (booking made, ticket opened, lead qualified). Your endpoint receives a JSON payload and does whatever you wire.
Best when: you already have an event-driven backend, or you want one outbound integration point.
03 / Bridge
Hand off to n8n, Make or Zapier. The agent runs your workflow and acts on the result — 3000+ apps reachable, no code on your side.
Best when: the destination is a long-tail SaaS without a direct connector — or you want non-engineers to wire the flow.
04 / MCP
Connect Model Context Protocol tools. Powers Cal.com and Meetergo today; the standard for newer AI-native systems.
Best when: the destination is an LLM-aware tool, or you want the agent to read context (docs, tickets) as well as act.
What it looks like in production
Each diagram below is a real path a call or message takes. Same Miyon agent in every case — only the systems on the other end change.
Flow 01 · Receptionist use case
Caller dials your customer's number. Agent picks up, qualifies the request, checks live availability in Cal.com, writes the booking, fires the SMS confirmation — all in the same call.
// Cal.com booking via native API (sample call)
POST /v2/bookings
{
"start": "2026-05-28T10:00:00+02:00",
"eventTypeId": "acme-plumbing-emergency-30",
"responses": { "name": "Sarah Klein", "phone": "+49308845…" },
"metadata": { "source": "miyon-receptionist", "callId": "ag_8214" }
}
→ 200 OK booking #bk_8214 · sms scheduled at T+0s
Total time from "Hello?" to "You'll get an SMS" — under 40 seconds. The agent never leaves the call; the integrations run inside the conversation, not after it.
Flow 02 · Lookup use case
The caller asks something only your data can answer. The agent calls your API mid-conversation, reads the answer back on the line, and emails a clean summary to your team.
// Live lookup via your REST API (sample call)
GET /v1/orders/5821
→ 200 OK { "status": "out_for_delivery", "eta": "2026-05-28T16:30" }
→ agent reads the ETA on the call · summary emailed to ops@your-brand.com
Flow 03 · Car dealership use case
A real, shipped integration: soft-nrg TKP. The caller reads out a licence plate; the agent resolves the make and model, finds the nearest workshop, and books the service — all on one call.
One real integration, end to end — licence plate to a booked service slot in a single call, no human in the loop.
Available now
Everything here is backed by code and runs live on the call. Don’t see your tool? It’s one webhook away (below) — or on the roadmap.
Reachable today via the API tool or the workflow bridge (n8n / Make / Zapier). Native connectors land next.
Under the hood
Every connected system becomes a "tool" in the agent's reasoning loop — with a typed contract, a permission scope, and an audit trail. The agent picks the right tool for the moment, calls it, reads the response, and continues the conversation.
Tool registry · sample
tools: - name: cal.book_slot scope: calendar.write args: event_type_id: string start: datetime attendee: { name, phone, email } returns: { booking_id, ics_url } - name: tkp.book_service scope: service.write args: plate: string branch_id: string slot: datetime returns: { booking_id, branch } - name: api.lookup_order scope: orders.read args: order_id: string returns: { status, eta }
3000+ apps, one webhook away.
No native connector for your tool? Bridge it through n8n, Make or Zapier — the agent runs your workflow and acts on the result, live on the call. No code.
Point the agent at any REST API, or bridge through n8n, Make or Zapier — live on the call, no native connector required. Native connectors for the tools your customers ask for most are on the roadmap.
Miyon AG · Whitelabel OEM partnerships · info@miyon.ai