Connect Chroma DB to IntelDialix voice agents

How it works

How information moves between a live phone call and Chroma DB.

1. 01

   A call reaches your agent

   A caller dials a Twilio or SIP number assigned to the agent, or the agent places an outbound call from a campaign.

   Twilio / SIP number → IntelDialix agent

2. 02

   The agent uses Chroma DB mid-call

   When the conversation needs data, the agent runs a custom tool: an HTTP request to Chroma DB with the details it has collected.

   Custom tool → Chroma Python SDK

3. 03

   The call ends with a record

   IntelDialix keeps the recording, transcript and post-call analysis for the conversation in your call history.

   Recording · transcript · analysis

4. 04

   Chroma DB receives the result

   A signed webhook delivers the call event to your Chroma DB endpoint, and is retried automatically if the delivery fails.

   HTTPS POST · X-Dialix-Signature

At a glance

Key figures

Voice engines

ElevenLabs · Vapi · Gemini

Choose the engine per agent and compare them on real calls.

Telephony

Twilio & SIP

Use numbers you already have, for inbound and outbound calls.

Call events

Signed webhooks

HMAC-SHA256 signature on every delivery, retried on failure.

Starter plan

$14 / month

One agent, one number and 100 calls a month.

Example

// Verify an IntelDialix webhook before trusting it in Chroma DB.
// Header: X-Dialix-Signature: t=<unix seconds>,v1=<hex>
// where v1 = HMAC-SHA256(secret, "<t>.<raw request body>")
import crypto from 'node:crypto';

export function verifyDialixWebhook(rawBody, signatureHeader, secret) {
  const parts = Object.fromEntries(
    signatureHeader.split(',').map((kv) => kv.split('='))
  );
  const expected = crypto
    .createHmac('sha256', secret)
    .update(`${parts.t}.${rawBody}`)
    .digest('hex');
  const valid =
    typeof parts.v1 === 'string' &&
    parts.v1.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(parts.v1), Buffer.from(expected));
  const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;
  return valid && fresh;
}

// Body: { "event": "call.completed", "payload": { ... }, "timestamp": "..." }

Check the signature before acting on an event in Chroma DB. The secret is the one you set when you add the webhook in IntelDialix settings.

FAQ

Frequently asked questions

Keep exploring

Related pages

• integrationQdrant Voice AI IntegrationHigh-speed filtered vector search providing personalized long-term memory for recurring telephone callers.
• integrationMilvus Voice AI IntegrationEnterprise billion-scale vector index querying vast technical documentation libraries during live phone calls.
• integrationSupabase Voice AI IntegrationStore caller records, dynamic variables, and conversation state in Postgres with real-time vector embeddings.
• integrationPinecone Voice AI IntegrationVector search that retrieves knowledge-base snippets for the agent while the caller is speaking.
• integrationWeaviate Voice AI IntegrationHybrid BM25 and vector search providing instantaneous factual grounding for phone agent technical questions.