Share Assistants Externally

With external assistants, you can make the assistants you’ve built in innoGPT available outside the platform—via a public link, on your own subdomain, or embedded directly on your website. This turns your internal assistant into, for example, a chatbot for website visitors, a support assistant, or a publicly accessible quote generator.

⚠️ Prerequisite: The API must be enabled. External assistants do not count toward your regular subscription quota; instead, they are billed through API usage. Before you can deploy an assistant externally, the API must be enabled in your workspace. The budget for all requests processed via external assistants is deducted from your API credit. Without the API enabled, the deploy function is not available to you.

Open Deploy

Open the assistant you want to share externally in the editor. In the top-right corner, you’ll find three buttons: Share, Test Assistant, and a three-dot menu (…).

  1. Click the three-dot menu in the top-right corner.

  2. Select Deploy from the dropdown.

The Deploy Area at a Glance

The Deploy section is divided into six tabs:

  • General – Basic information for the public page

  • Branding – Colors, header, and footer

  • Settings – Behavior and security options

  • Domain – Free subdomain or your own domain

  • Share – Share link and embed website

  • Analytics – Usage Statistics

In the top right corner, you’ll see the Publish button. Only after publishing will the status change to Live, and your assistant will be accessible externally.

1. General – Basic Settings

Here you can customize how your assistant appears to visitors.

  • Description: A short description that appears below the assistant’s name on the public page.

  • Welcome Message: The first message visitors see before they ask their own question. Ideal for providing context or making it easier to get started.

  • Password Protected: A toggle that lets you restrict access with a password. Useful for internal testing or closed user groups. It’s also helpful to prevent unauthorized users from using up your API credits.

As long as the assistant isn’t published, you’ll see the message “Publish to enable chat preview…” in the preview on the right.

2. Branding – Customize the Look and Feel

In the Branding tab, you can customize the appearance to match your company.

Colors:

  • Primary Color: The main color of the interface.

  • Chat Bubble Color: Color of the assistant’s messages.

  • User Bubble Color: Color of user messages.

You can set each color using a hex code (e.g., #6366f1) or the color picker.

Header and Footer:

  • Show Header: Show or hide the header. Optionally, you can enter your own header text, which will override the assistant’s name.

  • Show Footer: Show or hide the footer and add your own footer text if needed (e.g., a legal notice link or notes).

Custom CSS: For advanced users: Use .public-chat-theme { /* your styles */ } to apply your own CSS rules to the public chat page and fully customize its appearance.

3. Settings – Control Behavior

In the Settings tab, you can configure, among other things, whether visitors must provide their email address (Require Email) before they can chat. This option is particularly relevant if you want to identify every visitor in the Analytics tab.

Publish the Wizard

Once all settings are correct:

  1. Click Publish in the top-right corner.

  2. The status will change to Live (green toggle in the top right corner).

  3. Your assistant is now accessible via the selected link, subdomain, or as an embed on your website.

  4. You can now access the three additional settings

You can make changes at any time; click “Save now” to apply them to the live version.

4. Domain – Set Accessibility

Here you specify the URL under which your assistant is accessible. There are two options to choose from:

Free Subdomain

Choose a custom name for your assistant’s subdomain at .agents.innogpt.de.

  1. Enter the desired name (lowercase letters, numbers, and hyphens only; 3–63 characters).

  2. Click Check to verify availability.

  3. Confirm by clicking “Save Subdomain.”

Example: dein-assistent.agents.innogpt.de

Custom Domain

If you want to run your assistant under your own domain (e.g., chat.deineseite.de), switch to the “Custom Domain” tab and follow the DNS instructions displayed there.

5. Share – Share and Embed

The Share tab is the heart of actively promoting your assistant.

Share Link

Anyone with this link can access your assistant (unless a password is set). Copy it directly or open it with a click.

Embed on Website (Embed via iFrame)

This is the most exciting feature for anyone who wants to use the assistant directly on their own website as a chat feature.

  1. Click on Show Code.

  2. Copy the generated iFrame code.

  3. Paste it into your website’s source code at the desired location.

The code looks something like this:

6. Analytics – Keep an Eye on Usage

Once your assistant is live, you’ll find all relevant usage data in the Analytics tab:

Overview:

  • Views: Number of page views.

  • Chats: Number of conversations held.

  • Engagement: Ratio of views to actual chats.

  • Days active: How long your assistant has been live.

  • Views/day: Average number of views per day.

Visitors: If you enable “Require Email” in the settings, you can identify each visitor via email. Without this option, you’ll only see anonymous numbers.

💡 Note: Email addresses are only collected if visitors actually enter them via the email gate or a sign-up form.

Timeline: Shows you when the assistant was published, plus other key dates.

Billing: Why the API Is Crucial

📌 Important Information About the Cost Structure All messages that go through an externally shared assistant—whether via a link, subdomain, or embed—are billed against your API budget, not your regular user subscription. There are two reasons for this:

  1. External users do not have a innoGPT account and therefore are not associated with a subscription.

  2. API billing is token-based and therefore scales fairly—you only pay for actual usage.

Keep an eye on your API budget, especially for heavily trafficked embeds on public websites.

Typical Use Cases

  • Chatbot on the company website: Embed a support assistant via an iFrame.

  • Landing page assistant: Newsletter creator, product advisor, or lead qualifier on a campaign page.

  • Internal, protected access: Assistant with password protection for selected user groups.

  • Custom tools: Assistant hosted under your own custom domain as part of your product portfolio.

If you have questions about API activation or billing details, contact your Workspace admin or innoGPT support.