> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tavus.io/llms.txt
> Use this file to discover all available pages before exploring further.

# App builders and website builders

> Use a prompt in Lovable, Replit, Bolt or v0, or paste a script tag into Webflow, Framer, Wix or Squarespace.

## Overview

A deployment needs nothing from your stack: the browser loads the element with a deployment id, and Tavus runs the conversation. That makes it a fit for two kinds of tools where you do not control the build.

* **AI app builders** such as Lovable, Replit, Bolt and v0 write the code for you from a prompt. Give their agent the [embed or widget prompt](/sections/deployments/coding-agents#choose-a-prompt) and your deployment id. In an editor that supports MCP, such as Cursor, Claude Code or Codex, [connect the Tavus MCP server](/sections/deployments/coding-agents#connect-the-tavus-mcp-server) instead and the agent creates the deployment itself.
* **Website builders** such as Webflow, Framer, Wix and Squarespace have no agent and no build step. Paste the script tag and the element into the site's custom code.

For both, create the deployment first in the [PAL Maker](https://maker.tavus.io) and keep its id at hand. The id is safe to expose; access is controlled by the deployment's allowed origins, call limits and bot protection, all set in the PAL Maker.

## AI app builders

<Card title="Get an embed or widget prompt" icon="robot" href="/sections/deployments/coding-agents#choose-a-prompt" horizontal cta="Choose a prompt">
  Open the prompt for your channel, copy its full text, and paste it into your project's chat.
</Card>

<Steps>
  <Step title="Paste the prompt">
    Open your project's chat and paste the [embed prompt](https://github.com/Tavus-Engineering/tavus-examples/blob/main/examples/embed-prompt.md) for a conversation inside the layout, or the [widget prompt](https://github.com/Tavus-Engineering/tavus-examples/blob/main/examples/widget-prompt.md) for a floating launcher. It tells the agent what the element can do, asks what you want to build, and points it at the [examples](/sections/deployments/examples) and this documentation. If you already know which shape you want (a section, a card that expands into a modal, a button that starts the call, a kiosk, a launcher the PAL can navigate from), say so in the same message.
  </Step>

  <Step title="Answer its questions">
    The agent asks where the element goes, which stack to keep, for your deployment id, and whether the PAL has tools for acting on the page. Give it the id as text; it is not a secret and does not need an environment variable or a secrets store.
  </Step>

  <Step title="Test on the published URL">
    Previews in these tools run inside an iframe. The call needs camera and microphone access, which some preview frames do not grant. If the preview stalls on permissions, publish the app and test there. Add the published domain to the deployment's allowed origins in the PAL Maker if you have restricted origins.
  </Step>
</Steps>

## Website builders

Copy the snippet for your deployment's channel. Replace `YOUR_DEPLOYMENT_ID` with your deployment id; no package install is needed.

<Tabs>
  <Tab title="Embed (inline)">
    ```html theme={null}
    <div style="width: 100%; max-width: 960px; aspect-ratio: 16 / 9; margin: 0 auto;">
      <tavus-embed deployment-id="YOUR_DEPLOYMENT_ID"></tavus-embed>
    </div>
    <script src="https://unpkg.com/@tavus/embed@latest"></script>
    ```
  </Tab>

  <Tab title="Widget (floating launcher)">
    ```html theme={null}
    <tavus-widget deployment-id="YOUR_DEPLOYMENT_ID"></tavus-widget>
    <script src="https://unpkg.com/@tavus/widget@latest"></script>
    ```
  </Tab>
</Tabs>

Where to paste it:

| Platform | Script tag | Element |
| - | - | - |
| **Webflow** | Site settings, Custom code, footer code (before `</body>`), or a page's custom code. | An Embed element on the page for the embed; the widget needs no element placement beyond the custom code. |
| **Framer** | Site settings, General, Custom code, end of `<body>`. | An Embed component set to HTML for the embed. |
| **Wix** | Settings, Custom code, body end. | An Embed HTML element (iframe-based embeds do not work; use the "Custom element" or "Embed code" option that injects into the page). |
| **Squarespace** | Settings, Advanced, Code injection, footer. | A Code block on the page. |

Three things apply to all of them:

* **Publish to see it.** Custom code runs on the published site, and often not in the editor's preview.
* **HTTPS is required.** Browsers only allow camera, microphone and WebRTC on secure pages. Published sites on these platforms are served over HTTPS.
* **The element fills its wrapper.** Give the embed a box with a definite size, usually `aspect-ratio: 16 / 9` on desktop and `9 / 16` on phones. The widget positions itself; it needs no wrapper.

<Info>
  Platform menus move. If a path above no longer matches, search the platform's help for "custom code" or "code injection"; the snippet itself does not change.
</Info>

## Next steps

<CardGroup cols={2}>
  <Card title="Build with a coding agent" icon="robot" href="/sections/deployments/coding-agents">
    Connect the Tavus MCP server, or copy the embed or widget prompt.
  </Card>

  <Card title="Examples" icon="code" href="/sections/deployments/examples">
    Six complete pages to read or copy.
  </Card>

  <Card title="Host communication" icon="tower-broadcast" href="/sections/deployments/host-communication">
    Start the call from your own button, read a transcript, answer tool calls.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.