Connect Predvora with the tools you already use.

Your representative answers visitors and captures enquiries on your website. These integrations carry that work into the rest of your day: a meeting booked from the chat, your leads in the assistant you already ask questions, a new enquiry in your CRM a few seconds after it happens.

Everything on this page is live today. Meeting scheduling and the assistant connection are included in every plan; webhooks and the API come with Professional and Business.

Meeting scheduling

Every plan

Visitors book a time with you without leaving the chat. You paste the link of your Cal.com or Calendly scheduling page once, and the chat shows that page in place whenever a visitor wants to meet.

What the visitor sees

  • A calendar button in the head of the chat and a Book a meeting button under the conversation. Both open your scheduling page inside the chat panel, on desktop and on phones.
  • A bar above the page with Back to the conversation and Open in a new tab. Going back returns to the conversation exactly where it was.
  • When a visitor asks to meet, call or schedule, the representative points to the button in one sentence. It never checks your availability and never books anything itself: the booking happens on your scheduling page, under your account there.

Set it up

  1. In your Predvora dashboard, open Integrations and find Meeting scheduling.
  2. Paste the public link of one event type, like https://cal.com/you/30min or https://calendly.com/you/30min, and save.
  3. Open your website. The button appears the next time the chat loads.

The link must be an https address on cal.com, on a cal.com subdomain (Cal.com organisations) or on calendly.com. Admins and editors can both set it. Removing the link removes the button.

If your website sets a Content-Security-Policy

The scheduling page loads in a frame inside the chat. If your site sends a Content-Security-Policy header with a frame-src directive, add cal.com or calendly.com to it. Without that the frame stays empty and the visitor can still use Open in a new tab.

Ask from your own page

Every plan

Any search box, form or button on your website can hand a question to your representative. The visitor types or clicks, the chat opens, and the answer starts at once.

A form or a search box

Add one attribute to the form. When a visitor submits it, the chat opens and sends what they typed.

<form data-predvora-ask>
  <input name="question" placeholder="Ask a question">
  <button>Ask</button>
</form>

A button, or your own script

Predvora.ask("Do you have parking?") opens the chat and sends the question. Predvora.open() only opens it.

<button onclick="Predvora.ask('Do you have parking?')">Do you have parking?</button>

Good to know

  • It works in every widget mode and on every plan. There is nothing to switch on.
  • A question asked this way is answered, and uses a credit, exactly like a typed one.
  • If the chat is not available on a page, a form keeps what the visitor typed.

The question buttons on predvora.com use exactly this. Try one:

Connect Predvora with Claude

Every plan

Add Predvora to Claude as a custom connector and ask about your leads, your conversations and what your representative knows, in the chat you already use.

Connector address

https://predvora.com/mcp

The address is the same for everyone. What an assistant can read is decided by the Predvora account you sign in with when you connect.

Connect

  1. In Claude, open Settings, then Connectors, and choose Add custom connector.
  2. Paste the connector address as the connector URL.
  3. Sign in to Predvora when Claude asks, and allow the connection.

Claude opens a Predvora page that names the workspaces it will be able to read. Allow it, and Predvora appears among your connectors with its eight read-only tools.

Predvora plugin in ChatGPT

Every plan

Add Predvora to ChatGPT as a custom MCP server and ask the same questions there.

Connector address

https://predvora.com/mcp

Connect

  1. In ChatGPT, open Plugins, choose Add, then Add custom MCP server.
  2. Paste the connector address as the server URL and create the plugin.
  3. Choose Connect, sign in to Predvora when ChatGPT asks, and allow the connection.

ChatGPT opens the same Predvora page, with the workspaces it will be able to read. Allow it, and the tools are available in your chats.

Which ChatGPT plans can add a custom MCP server is decided by OpenAI.

What an assistant can read

The connection gives an assistant eight tools. Each one reads; none writes.

List workspaceslist_workspaces
The workspaces you belong to, with each website and whether its representative is live.
Get workspace overviewget_overview
One workspace at a glance: the representative's status, the domain's verification, and how many conversations, leads and requests the last 30 days brought.
List leadslist_leads
The leads your representative captured, newest first, with contact details, a summary and their status. Can be narrowed by status and by date.
Get a leadget_lead
One lead in full, with what the visitor asked for and the last twenty messages of the conversation it came from.
List conversationslist_conversations
Visitor conversations, newest first: when, where from, what about, how they ended. Can be narrowed by topic, outcome, source and date.
Get a conversationget_conversation
One conversation with its transcript, its summary and the lead it produced, if any.
Search conversationssearch_conversations
Conversations whose summary or topic contains the words you name.
List knowledge factslist_knowledge_facts
The facts your representative answers from, with their type, where each came from and whether you edited it.

A transcript is served up to its newest 60 messages or 20,000 characters, and says so when earlier messages were left out. Lists come 25 entries at a time, 100 at most. Your own test chats are included and marked as tests. One connection may make 60 requests a minute and 2,000 a day.

What it can do

  • Read the leads, conversations, transcripts and knowledge of the workspaces you belong to, as your own dashboard shows them.
  • Answer questions across them: summarise a week, find a conversation, compare what visitors asked.
  • Tell you when something is not there, in a sentence that says what to try next.

What it cannot do

  • Change, add or delete anything. There is no tool for it, so a request to delete a lead or add a fact ends with the assistant saying so.
  • Answer your visitors or speak as your representative.
  • Read another customer's data, or a workspace you are not a member of.
  • See billing, plans or credit balances. None of it is served.
  • Spend credits. Reading through an assistant is free of charge.

Things to ask

  • Which leads came in this week, and what did each one want?
  • Show me the conversation behind the lead from Priya.
  • What did visitors ask about most in the last thirty days?
  • What does my representative know about our opening hours?

Disconnect

In your Predvora dashboard, open Integrations. Connected assistants lists every assistant connected to your account with the time it last read something. Revoke ends the connection at once: the assistant's next request is refused until you connect again. You can also remove the connector inside Claude or ChatGPT.

Webhooks

Professional and Business

A webhook sends a small signed JSON message to an address of yours the moment something happens: a lead is captured, a visitor asks for a follow-up, a conversation ends. It is how Predvora reaches a CRM, a spreadsheet, a chat channel or any automation tool.

A workspace admin adds endpoints in the dashboard under Integrations, Webhooks: the address, the events it should receive, and Send test event to try it. The address must be a public https URL on the default port, without credentials in it. A workspace can have up to 5 endpoints.

Events

lead.created
The representative captured a lead: a visitor left an email address or a phone number.
outcome.created
A visitor asked for something to happen next, such as a callback, an appointment, a quote or a person to talk to.
conversation.closed
A conversation ended: about half an hour passed without a new message.

Events are sent for conversations with real visitors on your website and your hosted page. Your own test chats and preview conversations never send one.

The payload

Every delivery is a POST with a JSON body of the same outline: the event's id and type, when it happened, the workspace, and the record under data. A lead arrives with its contact details and summary. A conversation arrives with its summary, topic and a link to it in your dashboard. No delivery carries a transcript.

{
  "id": "evt_9f2c4b7a1e5d4c3b8a6f0e1d2c3b4a59",
  "type": "lead.created",
  "created_at": "2026-11-12T09:41:07.000Z",
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic",
    "website": "aurora-dental.example"
  },
  "data": {
    "lead": {
      "id": "c7a9e2d4-51b3-4e8f-a6c0-9d2b7f3e1a48",
      "created": "2026-11-12T09:41:05.512Z",
      "name": "Priya Nair",
      "email": "priya@example.com",
      "phone": null,
      "summary": "Broke a molar and wants an appointment this week, mornings preferred.",
      "qualification": "Urgent need this week and reachable by email.",
      "status": "new",
      "conversationId": "e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20",
      "preferredChannel": "email",
      "preferredTime": "mornings",
      "context": null,
      "outcome": {
        "type": "appointment_request",
        "status": "new",
        "created": "2026-11-12T09:41:05.540Z"
      }
    }
  }
}

Headers

Predvora-Signature
A timestamp and a signature of the body, as t=<unix seconds>,v1=<hex>. See below.
Predvora-Event
The event type, like lead.created.
Predvora-Delivery
The event's id. It is the same on every retry of that event, so store it to recognise a repeat.
Content-Type
application/json

Verify the signature

Each endpoint has its own signing secret, shown once when you add the endpoint. The signature is the HMAC-SHA256 of the timestamp, a full stop and the raw request body, under that secret, in hex. Compute it over the bytes as received, before any JSON parsing, and refuse a timestamp that is too old. In Node.js, without a dependency:

const crypto = require("node:crypto");

function verifyPredvoraSignature(secret, header, rawBody, toleranceSeconds = 300) {
  const parts = Object.fromEntries(
    String(header || "")
      .split(",")
      .map((part) => part.trim().split("=")),
  );
  const timestamp = Number(parts.t);
  if (!timestamp || Math.abs(Date.now() / 1000 - timestamp) > toleranceSeconds) {
    return false;
  }
  const expected = crypto
    .createHmac("sha256", secret)
    .update(parts.t + "." + rawBody)
    .digest();
  const given = Buffer.from(String(parts.v1 || ""), "hex");
  return given.length === expected.length && crypto.timingSafeEqual(given, expected);
}

The example refuses a signature older than 5 minutes. Every retry is signed again with a fresh timestamp.

Retries and the switch-off rule

Answer with any 2xx status once you have stored the event. Do slow work afterwards; redirects are not followed. Predvora waits 10 seconds for the answer. When your receiver does not answer with a 2xx, the event is sent again up to 5 more times, after 30 seconds, 90 seconds, 4.5 minutes, 13.5 minutes and 40 minutes: 6 attempts over about an hour.

An event whose attempts all failed counts as one failed delivery. After 20 failed deliveries in a row, with no success between them, the endpoint is switched off and its card in the dashboard says so. Switching it back on in the dashboard starts a fresh count. A test event never counts.

Zapier, Make and n8n

Predvora has no app inside these tools and needs none. Each has a webhook trigger that gives you an address; that address becomes an endpoint in your dashboard.

Zapier

  1. In Zapier, create a Zap that starts with Webhooks by Zapier and the event Catch Hook.
  2. Copy the webhook URL Zapier shows and add it as an endpoint under Webhooks in your Predvora dashboard.
  3. Pick the events, then send a test event so Zapier can read the fields.

Make

  1. In Make, create a scenario that starts with the Webhooks module and Custom webhook.
  2. Copy the address Make gives the webhook and add it as an endpoint under Webhooks in your Predvora dashboard.
  3. Pick the events, then send a test event so Make learns the data structure.

n8n

  1. In n8n, add a Webhook node to a workflow and set its method to POST.
  2. Copy the node's production URL and add it as an endpoint under Webhooks in your Predvora dashboard.
  3. Pick the events, activate the workflow, then send a test event.

API reference

Professional and Business

A small read-only API over the same data: your leads, your conversations and the facts your representative answers from, as JSON. Use it for a report, a sync into your own database or a script.

Authentication

A workspace admin creates keys in the dashboard under Integrations, API access. A key looks like pv_live_ followed by 32 characters, is shown once, and reads exactly one workspace. Send it as a bearer token on every request:

curl "https://predvora.com/api/v1/overview" \
  -H "Authorization: Bearer pv_live_..."
  • Requests are GET only and answers are JSON, never cached.
  • Reading uses no credits.
  • Revoke a key in the dashboard and its next request is refused.
  • A workspace can have up to 10 keys at a time.

Endpoints

EndpointReturnsParameters
GET /api/v1/overviewThe workspace at a glance: representative, domain verification, and the last 30 days in numbers.none
GET /api/v1/leadsLeads, newest first.status, since, until, limit, cursor
GET /api/v1/leads/{id}One lead with its contact preferences, the outcome the visitor asked for and the last twenty messages of its conversation.none
GET /api/v1/conversationsConversations, newest first, without their messages.since, until, intent, outcome, source, limit, cursor
GET /api/v1/conversations/{id}One conversation with its transcript and the id of the lead it produced, if any.none
GET /api/v1/knowledge/factsThe facts the representative answers from.type, limit, cursor

Every answer starts with the workspace the key belongs to, then the result. A conversation's transcript is its newest 60 messages or 20,000 characters, with truncated set to true when earlier messages were left out; a lead carries the last 20 messages of its conversation.

Parameters

status
Leads with this status: new, qualified, contacted, converted or closed.
since
Entries created at or after this ISO 8601 date or date-time, like 2026-11-01 or 2026-11-01T09:00:00Z.
until
Entries created at or before this ISO 8601 date or date-time.
intent
Conversations with exactly this detected topic, as a list returns it (upper and lower case do not matter).
outcome
Conversations that ended with this request, such as callback_request or appointment_request.
source
Conversations from this source: widget, drawer, standalone (your hosted page) or test (your own test chats).
type
Facts of this type, such as hours, service, contact or policy.
limit
How many entries to return, 1 to 100. The default is 25.
cursor
The nextCursor of the previous page.

Pagination

Lists are newest first. Each answer carries nextCursor: pass it back as cursor to get the next page, and stop when it is null. A cursor belongs to the list that issued it.

Errors

An error is a JSON object with a stable error code, a message that says what to do, and for a bad parameter the field it concerns.

StatuserrorMeaning
400invalid_rangeA parameter is out of range or malformed. The message names it, and field carries its name.
401unauthorizedThe key is missing, malformed, unknown or revoked.
403not_entitledThe workspace's plan does not include API access.
403account_suspendedThe workspace is suspended.
404lead_not_foundNo lead with that id in the key's workspace.
404conversation_not_foundNo conversation with that id in the key's workspace.
429rate_limitedToo many requests. retry_after and the Retry-After header say how many seconds to wait.
500unavailableThe read could not be completed. Try again in a moment.

Rate limits

Each key may make 60 requests a minute and 2,000 a day. Past that the answer is 429 rate_limited with a Retry-After header. A key used on the connector address shares the same allowance.

Examples

curl "https://predvora.com/api/v1/overview" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "overview": {
    "workspace": {
      "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
      "name": "Aurora Dental Clinic",
      "website": "aurora-dental.example"
    },
    "representative": {
      "name": "Aurora Assistant",
      "status": "live"
    },
    "domain": {
      "domain": "aurora-dental.example",
      "status": "verified",
      "method": "script_install"
    },
    "period": {
      "days": 30,
      "conversations": 214,
      "leads": 37,
      "outcomes": 29
    }
  }
}
curl "https://predvora.com/api/v1/leads?status=new&since=2026-11-01&limit=1" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "leads": [
    {
      "id": "c7a9e2d4-51b3-4e8f-a6c0-9d2b7f3e1a48",
      "created": "2026-11-12T09:41:05.512Z",
      "name": "Priya Nair",
      "email": "priya@example.com",
      "phone": null,
      "summary": "Broke a molar and wants an appointment this week, mornings preferred.",
      "qualification": "Urgent need this week and reachable by email.",
      "status": "new",
      "conversationId": "e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20"
    }
  ],
  "nextCursor": "eyJ0IjoiMjAyNi0xMS0xMlQwOTo0MTowNS41MTJaIiwiaWQiOiJjN2E5ZTJkNC01MWIzLTRlOGYtYTZjMC05ZDJiN2YzZTFhNDgifQ"
}
curl "https://predvora.com/api/v1/leads/c7a9e2d4-51b3-4e8f-a6c0-9d2b7f3e1a48" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "lead": {
    "id": "c7a9e2d4-51b3-4e8f-a6c0-9d2b7f3e1a48",
    "created": "2026-11-12T09:41:05.512Z",
    "name": "Priya Nair",
    "email": "priya@example.com",
    "phone": null,
    "summary": "Broke a molar and wants an appointment this week, mornings preferred.",
    "qualification": "Urgent need this week and reachable by email.",
    "status": "new",
    "conversationId": "e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20",
    "preferredChannel": "email",
    "preferredTime": "mornings",
    "context": null,
    "outcome": {
      "type": "appointment_request",
      "status": "new",
      "created": "2026-11-12T09:41:05.540Z"
    },
    "transcriptExcerpt": [
      {
        "role": "visitor",
        "at": "2026-11-12T09:38:12.201Z",
        "text": "I broke a molar last night. Can I come in this week?"
      },
      {
        "role": "representative",
        "at": "2026-11-12T09:38:15.874Z",
        "text": "I'm sorry to hear that. The clinic keeps emergency appointments on weekdays. If you leave your name and an email address or phone number, the team will confirm a time with you."
      },
      {
        "role": "visitor",
        "at": "2026-11-12T09:40:58.330Z",
        "text": "Priya Nair, priya@example.com. Mornings are best."
      }
    ]
  }
}
curl "https://predvora.com/api/v1/conversations?source=widget&limit=1" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "conversations": [
    {
      "id": "e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20",
      "started": "2026-11-12T09:38:12.201Z",
      "closed": "2026-11-12T10:11:00.000Z",
      "status": "closed",
      "source": "widget",
      "test": false,
      "intent": "emergency appointment",
      "outcome": "appointment_request",
      "summary": "Visitor broke a molar and asked for an appointment this week; left a name and email.",
      "messageCount": 6
    }
  ],
  "nextCursor": null
}
curl "https://predvora.com/api/v1/conversations/e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "conversation": {
    "id": "e4d8b1f6-2a7c-4c39-b5e0-7f1a3c9d6b20",
    "started": "2026-11-12T09:38:12.201Z",
    "closed": "2026-11-12T10:11:00.000Z",
    "status": "closed",
    "source": "widget",
    "test": false,
    "intent": "emergency appointment",
    "outcome": "appointment_request",
    "summary": "Visitor broke a molar and asked for an appointment this week; left a name and email.",
    "messageCount": 6,
    "leadId": "c7a9e2d4-51b3-4e8f-a6c0-9d2b7f3e1a48",
    "transcript": [
      {
        "role": "visitor",
        "at": "2026-11-12T09:38:12.201Z",
        "text": "I broke a molar last night. Can I come in this week?"
      },
      {
        "role": "representative",
        "at": "2026-11-12T09:38:15.874Z",
        "text": "I'm sorry to hear that. The clinic keeps emergency appointments on weekdays. If you leave your name and an email address or phone number, the team will confirm a time with you."
      },
      {
        "role": "visitor",
        "at": "2026-11-12T09:40:58.330Z",
        "text": "Priya Nair, priya@example.com. Mornings are best."
      }
    ],
    "truncated": false
  }
}
curl "https://predvora.com/api/v1/knowledge/facts?type=hours" \
  -H "Authorization: Bearer pv_live_..."

200

{
  "workspace": {
    "id": "3b1f6a52-8c0e-4f7d-9a35-2d4e6f8a1c07",
    "name": "Aurora Dental Clinic"
  },
  "facts": [
    {
      "id": "a1c3e5f7-9b2d-4f60-8e1a-3c5d7f9b1e24",
      "type": "hours",
      "content": "Open Monday to Friday, 8:00 to 18:00. Emergency appointments on weekdays.",
      "edited": true,
      "source": "https://aurora-dental.example/contact",
      "created": "2026-10-02T14:20:11.000Z"
    }
  ],
  "nextCursor": null
}
curl "https://predvora.com/api/v1/leads?limit=500" \
  -H "Authorization: Bearer pv_live_..."

400

{
  "error": "invalid_range",
  "message": "limit must be a whole number from 1 to 100.",
  "field": "limit"
}

Build your own

If you run your own agent or internal tool, you have two ways in, with the same data behind both.

The API
Plain HTTPS and JSON, for scripts, reports and syncs. Everything in the reference above.
The connector address with an API key
The address Claude and ChatGPT use also accepts an API key as the bearer token, in place of a sign-in. An agent that speaks the Model Context Protocol gets the same eight read-only tools for the key's workspace, with nobody at a browser. The server answers POST requests over Streamable HTTP and keeps no session.
curl -X POST "https://predvora.com/mcp" \
  -H "Authorization: Bearer pv_live_..." \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A key reads one workspace and never writes. Give each tool its own key, named after it, so you can revoke one without touching the others.

Privacy

Nothing on this page sends data anywhere until you set it up, and each piece can be taken away again in one place.

Meeting scheduling

Predvora sends nothing from the conversation to Cal.com or Calendly. The visitor's browser loads your scheduling page, and what the visitor types there goes to that provider under your account with them.

Remove the link under Integrations, Meeting scheduling.

Claude and ChatGPT

Only what the assistant asks for, when it asks, in a chat of a person who signed in to Predvora and allowed the connection. The answer becomes part of that person's chat with Anthropic or OpenAI, under their own terms with that company. It is limited to the workspaces that person belongs to.

Revoke under Integrations, Connected assistants. Each person revokes their own connections.

Webhooks

The event's record (for a lead: the contact details and summary the visitor gave) to the address an admin entered, each time a chosen event happens. Never a transcript.

Delete the endpoint, or switch it off, under Integrations, Webhooks.

API

What a request with one of your keys asks for, to whoever holds the key. Nothing is sent without a request.

Revoke the key under Integrations, API access.

Signing secrets and API keys are shown once. Store them like passwords, and replace one you think has been seen by someone else: delete or revoke it and create a new one.

Privacy policyHow we handle your data

On WordPress? The Predvora plugin puts the representative on your site in a few clicks.

Install on WordPressPlans and what each includes

See your representative before you pay

The free preview is the real thing: same answers, same manners. The only limits are volume. No card required.