Ingestion

Floe's ingestion pipeline reads your product's content and transforms it into the knowledge the AI agent uses to demo, onboard, and support users.

After you've created a site, ingestion is how you feed Floe the information it needs. The pipeline handles reading, processing, and indexing automatically.

How ingestion works

You give Floe the URLs to your content. Floe reads everything, processes it, and makes it available to the AI agent. When the agent is on a demo call or helping a user with in-app guidance, it draws on this knowledge to give accurate, contextual answers about your product.

Supported content types

  • Documentation: Product docs sites. Best for feature references, setup guides, API docs.
  • Knowledge Base: Help center articles. Best for FAQ, troubleshooting, how-to guides.
  • Changelog: Release notes. Best for what's new, version history.
  • YouTube Video: Video transcripts. Best for product walkthroughs, tutorials.
  • Loom Video: Loom recordings. Best for internal demos, feature explanations.
  • Image Gallery: Screenshots, diagrams. Best for visual product reference.

Adding an ingestion config

  1. Go to your site in the dashboard
  2. Open the Ingestion tab
  3. Click Add Config
  4. Select the content type
  5. Enter the source URL
  6. Save and the pipeline starts automatically

You can add multiple configs per site. A typical setup might include your docs site (Documentation), your help center (Knowledge Base), and a few product walkthrough videos (YouTube).

Content handling

Floe handles JavaScript-heavy sites and single-page applications. It stays within the same domain and respects robots.txt.

Running ingestion multiple times won't create duplicate entries. Updated content at the same URL replaces the previous version.

Monitoring ingestion

The Ingestion tab shows the status of each config:

  • Pending: Queued for processing
  • Processing: Currently reading and indexing
  • Completed: All content ingested successfully
  • Failed: Something went wrong (check the error message)

Typical processing time is 2-5 minutes for a small docs site (50-100 pages).

What's next

Once content is ingested, run exploration from the Explorer tab to map your product's UI, then generate capabilities from the Capabilities tab. See the Quickstart for the full flow, or learn more about how it works.

FAQ

Can I ingest content behind a login? Floe handles authenticated content sources. Configure access during setup.

What if my docs site changes frequently? Re-run ingestion any time. Updated content replaces the previous version automatically.

Is there a limit on how much content I can ingest? No hard limit. Most products ingest 50-200 pages. Larger knowledge bases work fine, they just take longer to process.