What Data Sources Does LLMStack Support for Connecting Your Own Data?

Updated

LLMStack supports importing your own data from Web URLs, Sitemaps, PDFs, Audio, PPTs, Google Drive, and Notion. Once imported, that data can be connected to LLM models to ground your generative AI apps and chatbots. This is part of LLMStack's no-code workflow, so you don't need to write ingestion code to get your content into an app.

Supported Data Sources

Based on LLMStack's own description of its "Bring your own Data" capability, the platform lists the following sources:

Source type Examples / notes
Web URLs Individual pages you point the platform at
Sitemaps Bulk discovery of pages from a site's sitemap
PDFs Document files
Audio Audio content
PPTs Presentation files
Google Drive Imports from your Drive
Notion Imports from Notion

The listing uses "including" and "etc.," which signals these are representative examples rather than a guaranteed exhaustive list. If you need a source that isn't named, treat it as unconfirmed rather than assumed to work.

How Imported Data Connects to Models

The purpose of importing data is to "connect it to LLM models to supercharge your generative AI applications and chatbots." In practice this means your imported content becomes the grounding material an app or chatbot draws on, rather than relying only on a model's built-in knowledge.

LLMStack also states it supports all major model providers, including OpenAI, Cohere, Stability AI, and Hugging Face. So the data-connection step and the model-choice step are separate: you bring content from the sources above, then attach it to whichever supported model you're using.

What This Means for a No-Code Build

Because data import sits inside a no-code flow, the practical sequence is:

  1. Choose a source from the supported list (for example, a PDF or a Notion page).
  2. Import that content into LLMStack.
  3. Connect the imported data to an LLM model.
  4. Build the app or chatbot on top of that grounded data.

You can also share the resulting app publicly or restrict access using LLMStack's permission model, with viewer and collaborator roles for building together.

Choosing a Source: Practical Considerations

  • Broad site coverage: A Sitemap is the more efficient option when you want many pages from one site rather than adding URLs one at a time.
  • Structured documents: PDFs and PPTs suit content that already exists as files.
  • Living workspaces: Google Drive and Notion imports make sense when your source material changes in those tools.
  • Audio: Useful when your knowledge lives in recordings rather than text.

What Isn't Specified

The available information does not state limits on file size, number of sources, refresh or sync frequency, or whether imports update automatically when the original source changes. It also doesn't detail authentication requirements for Google Drive or Notion. If any of these matter for your use case, verify them directly with LLMStack before committing.