Odeo

The AI chatbot for Webflow

Odeo answers questions about your product, pricing and integrations on your Webflow website and turns interest into an inquiry. Embedded with one script tag, no app.

  • Added under Site settings › Custom code
  • Reads pages and CMS collections
  • Requires a paid Webflow plan
See pricing Talk to us
  • Hosting and data in Switzerland1
  • Set up in under 30 minutes2
  • From CHF 39 per month3

Odeo · AI assistant

your-website.com

Example

Is there an integration with HubSpot?

Yes, contacts and inquiries go straight into HubSpot. Shall I suggest a demo with our team?

Runs on Webflow

No plugin, no app

On your Webflow website in three steps

  1. 1Enter your website URL

    Odeo reads your website and builds the knowledge base from it. You add PDFs and documents in the client portal.

  2. 2Tailor it in the client portal

    Colours, tone, role and behaviour, plus the pages on which the chatbot appears.

  3. 3Add the script tag

    Add the line under Site settings › Custom code in the “Footer code” field and publish the site. It then applies to every page.6

Add it to

Site settings Custom code Footer code

then publish the site

Webflow only allows custom code in the site settings on a paid plan.

Your line of code, with your key in the client portal

<script
  src="https://chat.sidora.ch/widget/chatbot.js"
  data-api-key="Your key" async></script>
No plugin, no app If needed, we support you with the setup.

What Odeo does on your Webflow website

  • Interest becomes an inquiry

    Odeo recognises buying interest, asks follow-up questions and hands qualified inquiries to your CRM.

    More about this feature

  • Questions about product and pricing

    Plans, features, integrations: Odeo answers from your pages, around the clock.

    More about this feature

  • Answers from your documents

    Odeo makes manuals, data sheets and release notes searchable via chat.

    More about this feature

Data directly from Webflow

Odeo reads pages and CMS collections automatically. For data from your CRM or your own application, we connect Odeo directly, without middleware. Direct connections are quoted per project.

  • Directly via existing interfaces such as REST API and webhooks
  • No middleware such as n8n or Zapier, no detours
  • If there is no interface, Sidora AG builds it
  • Direct integrations are quoted per project
How the direct integration works
Odeo
No middleware
  • Webflow CMS
  • HubSpot
  • Your web app
  • Webhooks
  • Your application Interface built by Sidora AG

Frequently asked questions

Answered briefly. We are happy to clarify anything else in person.

Get in touch +41 44 500 25 55
Do I need a Webflow app for Odeo?

No. Odeo is embedded with one script tag in the footer code of the site settings. There is no Odeo app to install.

Which Webflow plan do I need?

Webflow only allows custom code in the site settings on a paid plan. After adding the line, publish the site so it goes live.

Can Odeo use content from the Webflow CMS?

Yes. Odeo reads all published pages, including the pages of your CMS collections. If data should come directly from the Webflow CMS, we connect Odeo via the Webflow API.

Will Odeo slow down my Webflow website?

No. The script loads asynchronously and does not hold up your pages. You control which pages the chatbot appears on in the client portal.

More platforms

All integrations

Odeo on your Webflow website.

Embedded without an app, tailored in the client portal. We are happy to advise you on connecting your CRM.

Get started Discuss integration

Developed and operated by Sidora AG, Winterthur

Notes

  1. Data residency in Switzerland applies as long as a local LLM is used. We run local LLMs such as Apertus, Llama or Mistral in Switzerland on request in the Enterprise plan.
  2. Typical set-up time for the website chatbot without connecting business applications.
  3. Starter plan, billed yearly. Billed monthly: CHF 49 per month.
  4. Requires a platform that allows custom code; some website builders only allow this on paid plans. All trademarks belong to their owners. Naming them shows technical compatibility, not a partnership.