Integrations

Overview

An integration is one connected account at an external service: a Shopify store, a Cal.com account, a Google Sheets login, your own Razorpay account. Once connected, its tools become available to your agents (see Voice agent tools).

Credentials you send are validated against the provider before they are stored, are stored encrypted, and are never returned by any endpoint. Responses only tell you whether a credential is stored (has_credentials).

A sheet automation watches one tab of a spreadsheet on a Google Sheets connection and acts on each new order row: it sends an approved WhatsApp template and/or has an agent call the customer, then writes the result back into the sheet. The agent-side behaviour (call variables, write-back columns) is described in Voice agent tools → Order automation from Google Sheets.

Authentication

Authorization: Bearer cm_your_api_key

Connecting a sign-in (OAuth) provider (Google Calendar & Gmail, Google Sheets, Shopify OAuth) is done in the console (Developer → Integrations), because it needs a person to approve it. Once connected, everything on this page works with a key.

Providers and credentials

POST /api/v1/integrations takes a provider and a credentials object whose shape depends on the provider. Send only the keys listed for the provider: calcom, hubspot, woocommerce, razorpay and manual reject any other key with 422.

The provider makes a real authenticated call to check the credentials. If it refuses, you get 422 with the reason (e.g. api_key is required, key id should look like rzp_live_… or rzp_test_…).

Use GET /api/v1/integrations/catalog for the live list of what can be connected.

The integration object

{
  "id": "6a1e…",
  "tenant_id": "a0b1…",
  "provider": "shopify",
  "name": "Main store",
  "status": "connected",
  "scopes": null,
  "external_account_id": "acme.myshopify.com",
  "has_credentials": true,
  "metadata": null,
  "created_at": "2026-09-20T06:10:00Z",
  "updated_at": "2026-09-20T06:10:00Z"
}

GET /api/v1/integrations

Returns an array of integration objects, newest first.

curl "https://api.callmissed.com/api/v1/integrations?limit=50" \
  -H "Authorization: Bearer cm_your_api_key"

POST /api/v1/integrations

curl -X POST https://api.callmissed.com/api/v1/integrations \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "calcom",
    "name": "Clinic bookings",
    "credentials": { "api_key": "cal_live_xxxxxxxx" }
  }'

Returns 201 with the integration object, status: "connected".

GET /api/v1/integrations/catalog

The gallery of connectable services, annotated with what this account already has connected. No credentials.

curl https://api.callmissed.com/api/v1/integrations/catalog \
  -H "Authorization: Bearer cm_your_api_key"

{
  "items": [
    {
      "provider": "calcom",
      "label": "Cal.com",
      "category": "scheduling",
      "auth_kind": "apikey",
      "logo_key": "calcom",
      "tool_names": ["calcom_list_slots", "calcom_book"],
      "enabled": true,
      "aggregator": false,
      "description": "Check availability and book appointments on the call.",
      "connected": true,
      "account": "dr-mehta"
    }
  ]
}

GET /api/v1/integrations/{integration_id}

One integration. 404 Integration not found.

curl https://api.callmissed.com/api/v1/integrations/{integration_id} \
  -H "Authorization: Bearer cm_your_api_key"

PATCH /api/v1/integrations/{integration_id}

Every field is optional; only the fields you send are changed.

curl -X PATCH https://api.callmissed.com/api/v1/integrations/{integration_id} \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "credentials": { "api_key": "cal_live_newkey" } }'

Returns the updated integration. 404 Integration not found; 422 if the new credentials are rejected or status is not one of the three values.

PUT /api/v1/integrations/{integration_id}/spreadsheets

Google Sheets connections only. Sets which spreadsheets agents may use through the connection. The list replaces the existing one.

curl -X PUT https://api.callmissed.com/api/v1/integrations/{integration_id}/spreadsheets \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "spreadsheets": ["https://docs.google.com/spreadsheets/d/1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789/edit"] }'

Each spreadsheet is opened with the connection's own Google access before it is accepted, so it must be one the connected Google account can reach and has granted to CallMissed. The connection only reaches files picked in the Google file picker (console → Tools → Connected apps → Google Sheets → Choose spreadsheets). Returns the updated integration with metadata.spreadsheets:

{
  "metadata": {
    "spreadsheets": [
      { "id": "1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789", "title": "Orders 2026", "sheets": ["Orders", "Returns"] }
    ]
  }
}

DELETE /api/v1/integrations/{integration_id}

Disconnects and deletes the integration and its stored credential. Its sheet automations are deleted with it. Returns 204. 404 Integration not found.

curl -X DELETE https://api.callmissed.com/api/v1/integrations/{integration_id} \
  -H "Authorization: Bearer cm_your_api_key"

Shopify

A Shopify store connects either with an Admin API access token (POST /api/v1/integrations, provider: "shopify") or with Shopify sign-in from the console.

GET /api/v1/integrations/shopify/oauth/status

Whether Shopify sign-in is available, so a UI can choose between the sign-in button and the access-token form. Scope integrations:read.

curl https://api.callmissed.com/api/v1/integrations/shopify/oauth/status \
  -H "Authorization: Bearer cm_your_api_key"

{ "configured": true }

GET /api/v1/integrations/shopify/pixel-snippet

Returns the JavaScript to paste into Shopify admin → Settings → Customer events → Add custom pixel, so storefront events (product viewed, added to cart, checkout started and completed) reach CallMissed for that store. Scope integrations:read.

curl "https://api.callmissed.com/api/v1/integrations/shopify/pixel-snippet?integration_id={integration_id}" \
  -H "Authorization: Bearer cm_your_api_key"

{ "snippet": "// CallMissed storefront tracking — paste into Shopify admin →\n// Settings → Customer events → Add custom pixel.\nvar CM_URL=…" }

The first call creates the store's pixel token and saves it on the integration; later calls return a snippet with the same token. Paste the snippet value as returned. 404 Shopify integration not found; 400 Integration has no shop domain.

Sheet automations

One automation covers one tab of one spreadsheet. The spreadsheet must already be on the Google Sheets connection's list (PUT …/spreadsheets). Each tab can have one automation.

How it behaves:

• Columns are matched by header name, case-insensitively and ignoring extra spaces. The header row is the first of the top 5 rows that has at least two filled cells, so a title row above the header is skipped.
• Orders already in the tab when the automation starts are left alone. Only rows that appear afterwards are acted on, each order key at most once.
• COD vs prepaid. A row is cod when its payment_column cell contains one of cod_values (case-insensitive); otherwise, or with no payment_column, it is prepaid. Each segment has its own WhatsApp and call switches.
• Calls are placed only inside call_window_start–call_window_end in timezone_name, and unanswered calls are retried up to max_attempts times.
• Write-back. The result is written to status_column and note_column (default CallMissed Status / CallMissed Note).

The automation object

{
  "id": "9b2c…",
  "integration_id": "6a1e…",
  "spreadsheet_id": "1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789",
  "sheet": "Orders",
  "enabled": true,
  "key_column": "Order ID",
  "phone_column": "Phone",
  "name_column": "Customer",
  "payment_column": "Payment",
  "cod_values": ["cod", "cash on delivery"],
  "status_column": "CallMissed Status",
  "note_column": "CallMissed Note",
  "cod_whatsapp": true,
  "cod_call": true,
  "prepaid_whatsapp": true,
  "prepaid_call": false,
  "whatsapp_template_id": "77aa…",
  "whatsapp_params": { "1": "Customer", "2": "Order ID" },
  "bot_id": "c3d4…",
  "from_number_id": "e5f6…",
  "timezone_name": "Asia/Kolkata",
  "call_window_start": 9,
  "call_window_end": 21,
  "max_attempts": 3,
  "default_country_code": "91",
  "baseline_done": true,
  "last_polled_at": "2026-09-25T08:01:00Z",
  "last_error": null,
  "created_at": "2026-09-25T07:55:00Z",
  "updated_at": "2026-09-25T08:01:00Z",
  "agent_prompt_ready": true
}

GET /api/v1/sheet-automations

Returns an array of automation objects, newest first.

curl https://api.callmissed.com/api/v1/sheet-automations \
  -H "Authorization: Bearer cm_your_api_key"

GET /api/v1/sheet-automations/columns

The detected header row of a tab, to pick column names before creating an automation.

curl "https://api.callmissed.com/api/v1/sheet-automations/columns?integration_id={integration_id}&spreadsheet_id=1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789&sheet=Orders" \
  -H "Authorization: Bearer cm_your_api_key"

{ "header_row": 2, "columns": ["Order ID", "Customer", "Phone", "Payment", "Total"] }

404 Google Sheets connection not found; 422 Choose this spreadsheet in the Google Sheets connection first; 422 Couldn't read the tab '<sheet>'; 409 Reconnect Google Sheets and try again.

POST /api/v1/sheet-automations

curl -X POST https://api.callmissed.com/api/v1/sheet-automations \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "integration_id": "6a1e0000-1111-2222-3333-444455556666",
    "spreadsheet_id": "1AbCdEfGhIjKlMnOpQrStUvWxYz0123456789",
    "sheet": "Orders",
    "key_column": "Order ID",
    "phone_column": "Phone",
    "name_column": "Customer",
    "payment_column": "Payment",
    "whatsapp_template_id": "77aa0000-1111-2222-3333-444455556666",
    "whatsapp_params": { "1": "Customer", "2": "Order ID" },
    "bot_id": "c3d40000-1111-2222-3333-444455556666",
    "from_number_id": "e5f60000-1111-2222-3333-444455556666"
  }'

Returns 201. The whole automation is checked against the live sheet and your account before it is saved:

PATCH /api/v1/sheet-automations/{automation_id}

Accepts any field from the object table except integration_id, spreadsheet_id and sheet (the tab an automation watches cannot be changed; delete it and create a new one). Send only the fields you want to change. An empty string clears an optional column such as payment_column.

When the automation is (or stays) enabled, the result is validated exactly as on create and the same 422/409 errors apply. Sending {"enabled": false} pauses it without re-checking the sheet.

curl -X PATCH https://api.callmissed.com/api/v1/sheet-automations/{automation_id} \
  -H "Authorization: Bearer cm_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "prepaid_call": true, "call_window_end": 20 }'

Returns the updated automation. 404 Automation not found.

GET /api/v1/sheet-automations/{automation_id}/orders

The orders this automation has acted on, newest first. Rows that were already in the tab when it started are not listed.

curl "https://api.callmissed.com/api/v1/sheet-automations/{automation_id}/orders?limit=50" \
  -H "Authorization: Bearer cm_your_api_key"

{
  "total": 1,
  "items": [
    {
      "id": "0d1e…",
      "order_key": "#1042",
      "segment": "cod",
      "phone_e164": "+919812345678",
      "whatsapp_status": "sent",
      "whatsapp_error": null,
      "call_status": "done",
      "call_attempts": 1,
      "call_error": null,
      "outcome": "confirmed",
      "note": "Customer confirmed delivery address.",
      "sheet_status": "Confirmed",
      "sheet_error": null,
      "created_at": "2026-09-25T08:03:00Z",
      "updated_at": "2026-09-25T08:09:00Z"
    }
  ]
}

404 Automation not found.

DELETE /api/v1/sheet-automations/{automation_id}

Stops the automation and deletes it with its order history. Returns 204. 404 Automation not found.

curl -X DELETE https://api.callmissed.com/api/v1/sheet-automations/{automation_id} \
  -H "Authorization: Bearer cm_your_api_key"

Errors

Managing integrations and automations consumes no credits. The WhatsApp messages and calls an automation makes are billed like any other message or call.