VorinChat Embed Docs

Install VorinChat on Any Website

Use the universal loader on Django, WordPress, static HTML, or any platform that accepts a script tag. This page shows the generic flow. Site-specific installs live inside the Install Hub.

Loader

Canonical embed endpoint

Loader URL https://chat.vorinvista.com/chat/embed.js

Onboarding

Recommended flow

  1. Create a site install from the Install Hub or ask a team admin to provision one.
  2. Copy the generated site key and confirm the target domains are in the allowlist.
  3. Place the loader once per site, ideally before ``.
  4. Open the site, trigger the launcher, and confirm the conversation lands in the correct workspace inbox.

Platform snippets

Use the right snippet shape

Generic HTML Static site, Webflow, Framer, custom frontend
<script
  src="https://chat.vorinvista.com/chat/embed.js"
  data-site-key="your_site_key_here"
  data-title="VorinChat Support"
  defer
></script>
Django template Shared base layout or page shell
<script
  src="https://chat.vorinvista.com/chat/embed.js"
  data-site-key="your_site_key_here"
  data-title="VorinChat Support"
  defer
></script>
WordPress block Custom HTML block, footer hook, or site-specific plugin
<script
  src="https://chat.vorinvista.com/chat/embed.js"
  data-site-key="your_site_key_here"
  data-title="VorinChat Support"
  defer
></script>
Shopify theme block Custom Liquid block or `theme.liquid` footer section
<script
  src="https://chat.vorinvista.com/chat/embed.js"
  data-site-key="your_site_key_here"
  data-title="VorinChat Support"
  defer
></script>

What to expect

Runtime behavior

Isolation

Each site install gets its own site key and domain boundary.

Iframe shell

The widget launches inside a hosted iframe so the client site does not need the full app codebase.

Visitor context

Page URL, title, path, and referrer flow into the support inbox for each conversation.

WordPress option

For live installs, the Install Hub can export a site-specific WordPress plugin zip with the site key already wired in.

External systems

API key auth and signed webhooks live in the integrations layer, so CRM or automation tooling can react to support events.