Skip to content
CallMissed
Book a demo

Explore CallMissed

Integrations

Integrations that are really plugged in

Every connection on this page exists in the product today. Switch one on and your agent gets new tools it can use mid-conversation — not a logo on a slide.

Read the webhook docsRequest an integration
A vintage patch bay with brass sockets and a few coloured cables looped between them

Connect one today, and the agent can use it on the next call

6 connectors live

  • Shopify

    CommerceSign in to your store

    Your agent can read the store mid-conversation: where an order is, what a product costs, which customer it is talking to — and start a draft order.

    Tools it adds (4)
    • shopify_order_status
    • shopify_product_lookup
    • shopify_customer_lookup
    • shopify_create_draft_order

  • WooCommerce

    CommerceRead-only REST key

    The same store lookups for a WordPress shop. You create a read-only key in WooCommerce and paste it in; there is no app to register.

    Tools it adds (3)
    • woocommerce_order_status
    • woocommerce_product_lookup
    • woocommerce_customer_lookup

  • Cal.com

    SchedulingAPI key

    Real availability, read while the caller is still on the line, and a booking made before they hang up.

    Tools it adds (2)
    • calcom_list_slots
    • calcom_book

  • Google Calendar & Gmail

    SchedulingGoogle sign-in

    Read a calendar, find a free slot, create or move an event, and send the confirmation from the connected Gmail address.

    Tools it adds (6)
    • google_calendar_list_events
    • google_calendar_find_free_slots
    • google_calendar_create_event
    • google_calendar_update_event
    • google_calendar_delete_event
    • gmail_send_email

  • HubSpot

    CRMPrivate-app token

    Call notes written by the AI after the conversation are pushed onto the matching HubSpot contact, so the CRM your team already lives in stays current.

    Tools depend on what you connect, so they are named by the system on the other side.

  • Custom MCP server

    Anything elseServer URL

    Point at any MCP server you run and its tools become the agent’s tools on the next call. This is the escape hatch for internal systems nobody else has a connector for.

    Tools depend on what you connect, so they are named by the system on the other side.

Not ready yet:CalendlySalesforceSlackNotion— the console shows these as not connectable rather than as a button that fails.

And the lines the customer is actually on

A connector gives the agent something to look up. A channel is the conversation itself — the number, the page, the inbox the message arrived in.

  1. WhatsApp Business

    Connect a business number through Meta’s Tech Provider onboarding, then manage numbers, templates and conversations from the same workspace.

    WhatsApp Business API

  2. Facebook & Instagram

    A Facebook Page and an Instagram business account connect through the same Meta flow. Read and reply to DMs and comments, and publish drafted posts.

    Ask about Meta setup

  3. Twilio inbound voice

    Bring a voice-capable Twilio number. Verified credentials and signed inbound call webhooks route the call straight into the voice pipeline.

    Read the Twilio setup guide

Or have us call you

Subscribe an endpoint you own and we post signed JSON when something happens. Destination URLs are checked before the first send, and every attempt is recorded so a failure can be inspected and replayed.

Pick an event to see what your endpoint receives.

Conversations

Calls

Campaigns

Money and keys

POST your-url · conversation.started · signed
{
  "event": "conversation.started",
  "timestamp": "2026-09-19T11:20:04.512000+00:00",
  "data": {
    "conversation_id": "c0ffee00-1111-2222-3333-444455556666",
    "channel": "whatsapp"
  }
}

Simulated example — field names in data vary by event; the envelope is what the docs specify.

Scoped REST API

One cm_ key, with only the scopes a given integration needs. Conversations, contacts, knowledge, agents and inference are all reachable from your own code.

Developer API

Your own HTTP tool

Store a bearer token, API key or approved header set in the tenant credential vault, then let a configured HTTP tool call your endpoint during a conversation.

Developer hub

Before you connect anything

Which integrations can I actually switch on today?
Shopify, WooCommerce, Cal.com, Google Calendar and Gmail, HubSpot, and a custom MCP server of your own. Alongside those, WhatsApp Business, Facebook and Instagram connect as channels through Meta, and a Twilio number connects for inbound voice. Anything listed as coming soon is rendered in the console as not connectable rather than as a button that fails.
What does connecting one actually give the agent?
Tools. A connected Shopify store adds order, product and customer lookups plus a draft-order action; Cal.com adds slot listing and booking; Google Calendar adds event read, create, update and delete, and Gmail adds send. The agent calls them mid-conversation and uses the answer in its next sentence.
My system is not on the list. What then?
Three ways in. Run an MCP server and connect it by URL, and its tools appear on the call. Or store a bearer token, API key or approved header set in the tenant credential vault and call your own HTTP endpoint as a tool. Or work the other direction and subscribe a webhook endpoint to the events you care about.
How are the credentials stored?
A connection belongs to one tenant. Credentials are validated by that provider’s connector before anything is saved, are sealed at rest, and are never returned by the API — not to you, not to anyone else in your workspace.
What do the webhooks look like?
JSON over HTTPS to a URL you own, signed so you can verify the delivery came from us. Destination URLs are validated before the first send, and every attempt is recorded with its outcome so a failed delivery can be inspected and replayed.
Does Twilio work for outbound calling too?
The documented Twilio integration covers inbound voice. Outbound calling runs on the platform’s own telephony rather than through your Twilio account.
Do I need an integration to use the API?
No. A scoped cm_ key reaches conversations, contacts, knowledge, agents and inference directly. Integrations exist so an agent can reach a system you own while it is talking to someone; the API exists so your own code can reach the platform.

Plug it into what you already run

Open an account, connect a store or a calendar, and give the agent something real to look up. If the system you need is missing, tell us what it has to do.

Start freeRequest an integration