Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.onsomble.ai/llms.txt

Use this file to discover all available pages before exploring further.

Before any workflow can go live, your website and Onsomble need to be connected. This connection is what lets AI assistants find the capabilities you’ve published — knowledge to query, processes to walk a customer through — instead of just seeing the business’s name somewhere in a generic answer. Without it, workflows you build in Onsomble won’t reach customers. With it, every AI assistant that follows the web can discover and use them.

​
What “connecting” actually does

Connecting publishes a small, discoverable surface on your business’s website. It’s lightweight — a file and a reference, typically — and it tells any AI assistant that visits the site:
  • This business uses Onsomble to publish capabilities for AI assistants
  • These capabilities are available — for example, a knowledge base the assistant can query, or a “get a quote” workflow it can walk a customer through
  • Here’s how to use them
AI assistants don’t need to know about Onsomble specifically. The connection follows web conventions they already understand, so the same setup works across ChatGPT, Claude, Gemini, Perplexity, and any future assistant that can read the web.

​
What you need

To connect a Site, you need the ability to publish something to the underlying website. That typically means one of:
  • Access to the website’s files or deployment — upload a small file, or add a reference in the site’s configuration
  • Access to the CMS or site builder — WordPress, Webflow, Squarespace, and similar platforms usually expose what you need via their admin interface
  • Working with whoever manages the site — if you don’t directly administer the website, loop in the developer, freelancer, or agency who does
Onsomble provides the exact content to publish, with plain instructions for each common setup. You don’t need to understand what the content does — just that it needs to go where Onsomble tells you to put it.

​
Connecting a Site

1

Open the Workflows section of the Site

From the Site dashboard, go to Workflows. If the Site isn’t connected yet, the first thing you’ll see is a setup screen.
2

Follow the platform-specific instructions

Onsomble will detect or ask about the platform your website runs on and give you tailored steps — whether that’s uploading a file, pasting a reference into a theme header, or adding a plugin configuration.If your platform isn’t detected and you’re not sure, the generic “upload a file to your root directory” path works for most self-hosted sites.
3

Verify the connection

Once the content is in place, Onsomble runs a verification check to confirm everything is reachable. This usually takes a few seconds.If verification fails, Onsomble tells you exactly what’s missing or misconfigured so you can fix it.

​
When verification fails

The most common reasons a connection doesn’t verify on first try:
Double-check the exact path Onsomble gave you. Case, trailing slashes, and file extensions all matter.
CDNs, reverse proxies, and some platforms cache aggressively. Purge the cache and try verification again.
If the site is behind a bot-protection service (Cloudflare, for example) it may be blocking Onsomble’s verification request. Whitelisting Onsomble’s check resolves this.
Some setups involve two pieces — the content itself and a reference pointing to it. Both need to be in place for verification to pass.
If none of these apply, contact [email protected] with the Site name and we’ll help work through it.

​
After the connection is live

Once the connection is verified, you’re ready to publish workflows. You can start with either side of the pillar:

Knowledge content

Publish curated information for AI assistants to query when customers ask about your business.

Action workflows

Build structured processes — quotes, bookings, eligibility checks — that customers can complete through their AI assistant.
Knowledge content and action workflows are independent. Publishing knowledge doesn’t require you to build any action workflows, and vice versa. Start with whichever gives the business faster value, and layer in the other later.