From 7ad62159b66078f7ba351da1bee6371f0ad5adc8 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Tue, 9 Jun 2026 16:57:39 +1000
Subject: [PATCH 01/11] docs: consolidate Knowledge Tool steps into one page
 and sync to live catalog
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Fold the per-step Knowledge Tool step pages into a single tabbed page in
the Knowledge section (Writing / Searching and reading groups), and verify
every step against the platform's transformations catalog:

- remove Advanced knowledge search (plain) — no longer exists as a Tool step
- add Upsert knowledge (heavily used, was undocumented)
- fix Knowledge search fields: drop hidden Vector field, add Use exact search
- true up field labels and the variable-typing guidance

Tab ids preserve the old anchors; old /build/tools/tool-steps/knowledge/*
URLs redirect to the matching tab. Snippet cards and cross-links updated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .../integrations/knowledge-tool-steps.mdx     |  25 +-
 build/knowledge/access-knowledge.mdx          |  29 --
 .../advanced-knowledge-retrieval.mdx          |  35 --
 build/knowledge/create-knowledge.mdx          | 253 +++-------
 build/knowledge/delete-knowledge.mdx          |  37 ++
 build/knowledge/enrich-with-tool.mdx          |   2 -
 build/knowledge/find-and-use-knowledge.mdx    | 199 --------
 build/knowledge/inactive-table-deletion.mdx   |   8 +-
 .../confluence.mdx                            |  37 ++
 .../google-drive.mdx                          |   8 +-
 .../integrated-knowledge-sources/notion.mdx   |   4 +-
 .../sharepoint.mdx                            |   2 +-
 build/knowledge/knowledge-tool-steps.mdx      | 432 +++++++++++++++++-
 .../use-snippets-for-quick-access.mdx         | 133 ++----
 .../advanced-knowledge-search-2m.mdx          |  36 --
 .../knowledge/advanced-knowledge-search.mdx   | 121 -----
 .../tool-steps/knowledge/delete-knowledge.mdx | 123 -----
 .../tool-steps/knowledge/get-knowledge.mdx    | 117 -----
 .../tool-steps/knowledge/insert-knowledge.mdx |  95 ----
 .../tool-steps/knowledge/knowledge-search.mdx |  84 ----
 .../tool-steps/knowledge/update-knowledge.mdx | 133 ------
 .../knowledge/using-variables-in-json.mdx     |  72 ---
 docs.json                                     |  83 +++-
 example-use-cases/few-shot-prompting.mdx      |   2 +-
 get-started/core-concepts/knowledge.mdx       |   8 +-
 get-started/key-concepts/knowledge.mdx        |  25 -
 26 files changed, 687 insertions(+), 1416 deletions(-)
 delete mode 100644 build/knowledge/access-knowledge.mdx
 delete mode 100644 build/knowledge/advanced-knowledge-retrieval.mdx
 create mode 100644 build/knowledge/delete-knowledge.mdx
 delete mode 100644 build/knowledge/find-and-use-knowledge.mdx
 create mode 100644 build/knowledge/integrated-knowledge-sources/confluence.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/advanced-knowledge-search-2m.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/advanced-knowledge-search.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/delete-knowledge.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/get-knowledge.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/insert-knowledge.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/knowledge-search.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/update-knowledge.mdx
 delete mode 100644 build/tools/tool-steps/knowledge/using-variables-in-json.mdx
 delete mode 100644 get-started/key-concepts/knowledge.mdx

diff --git a/_snippets/components/integrations/knowledge-tool-steps.mdx b/_snippets/components/integrations/knowledge-tool-steps.mdx
index 8618e28b..2fa306cc 100644
--- a/_snippets/components/integrations/knowledge-tool-steps.mdx
+++ b/_snippets/components/integrations/knowledge-tool-steps.mdx
@@ -1,23 +1,26 @@
 <Columns cols={2}>
-  <Card href="/build/tools/tool-steps/knowledge/insert-knowledge" title="Insert Knowledge">
+  <Card href="/build/knowledge/knowledge-tool-steps#insert-knowledge" title="Insert knowledge">
     Use a Tool step to insert data to your knowledge table.
   </Card>
-  <Card href="/build/tools/tool-steps/knowledge/delete-knowledge" title="Delete Knowledge">
-    Use a Tool step to delete data from your knowledge table.
+  <Card href="/build/knowledge/knowledge-tool-steps#upsert-knowledge" title="Upsert knowledge">
+    Use a Tool step to insert or update rows by an identifier field.
   </Card>
-  <Card href="/build/tools/tool-steps/knowledge/update-knowledge" title="Update Knowledge">
+  <Card href="/build/knowledge/knowledge-tool-steps#update-knowledge" title="Update knowledge">
     Use a Tool step to update data in your knowledge table.
   </Card>
-  <Card href="/build/tools/tool-steps/knowledge/knowledge-search" title="Knowledge Search">
+  <Card href="/build/knowledge/knowledge-tool-steps#delete-knowledge" title="Delete knowledge">
+    Use a Tool step to delete data from your knowledge table.
+  </Card>
+  <Card href="/build/knowledge/knowledge-tool-steps#get-knowledge" title="Get knowledge">
+    Use a Tool step to get data from your knowledge table through search filters.
+  </Card>
+  <Card href="/build/knowledge/knowledge-tool-steps#knowledge-search" title="Knowledge search">
     Use a Tool step to search your knowledge table.
   </Card>
-  <Card href="/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m" title="Advanced Knowledge Search (2m)">
+  <Card href="/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context" title="Advanced knowledge search (2m)">
     Use a Tool step to search your knowledge table with a prompt.
   </Card>
-  <Card href="/build/tools/tool-steps/knowledge/advanced-knowledge-search" title="Advanced Knowledge Search">
-    Use a Tool step to search your knowledge table with more accuracy.
-  </Card>
-  <Card href="/build/tools/tool-steps/knowledge/get-knowledge" title="Get Knowledge">
-    Use a Tool step to get data from your knowledge table through search filters.
+  <Card href="/build/knowledge/knowledge-tool-steps#using-variables-in-json" title="Using variables in JSON">
+    Reference Tool inputs and other step outputs in your knowledge JSON fields.
   </Card>
 </Columns>
diff --git a/build/knowledge/access-knowledge.mdx b/build/knowledge/access-knowledge.mdx
deleted file mode 100644
index 7e24c5c8..00000000
--- a/build/knowledge/access-knowledge.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: 'Knowledge'
-sidebarTitle: 'Access knowledge'
-description: "Give your agents an tools access to knowledge"
----
-
-## Give your tool access to knowledge
-
-To give your tool access to knowledge, select the **Knowledge search** tool step. Then, select the knowledge table you want to search, type in your query and select between **keyword** (search for a specific word) or **vector** (search for relevant information).
-
-<div
-  style={{
-    width: '100%',
-    position: 'relative',
-    paddingTop: '61.46%',
-  }}>
-  <iframe
-    src="https://fast.wistia.com/embed/medias/f6stgrrzl8"
-    frameBorder="0"
-    style={{
-      position: 'absolute',
-      top: 0,left: 0, width: '100%', height: '100%',
-      borderRadius: '10px',
-    }}/>
-</div>
-
-## Give your agents access to knowledge
-
-To give your agents access to knowledge, make a tool, add the **Knowledge search** step, and give your agent your tool.
diff --git a/build/knowledge/advanced-knowledge-retrieval.mdx b/build/knowledge/advanced-knowledge-retrieval.mdx
deleted file mode 100644
index bedb5762..00000000
--- a/build/knowledge/advanced-knowledge-retrieval.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: 'Knowledge'
-sidebarTitle: 'Advanced'
-description: "Advanced knowledge retrieval"
----
-
-<div
-  style={{
-    width: '100%',
-    position: 'relative',
-    paddingTop: '61.46%',
-  }}>
-  <iframe
-    src="https://fast.wistia.com/embed/medias/6ptgbgeqyd"
-    frameBorder="0"
-    style={{
-      position: 'absolute',
-      top: 0,left: 0, width: '100%', height: '100%',
-      borderRadius: '10px',
-    }}/>
-</div>
-
-## Better knowledge retrieval
-
-Relevance provides a knowledge search step in our tool builder, but advanced users may want more control over the process to achieve more precise results.
-
-For more advanced knowledge retrieval, you can implement a series of steps in your tool.
-
-- **Query Refinement:** add a LLM step and give it a prompt that asks it to refine a user's free-form query into a more effective search query. This process removes filler words and focuses on the core intent of the question.
-- **Vector Search:** Add a knowledge search step where the refined query can be used in a vector search of a knowledge table. Vector search goes beyond simple text matching, looking for semantic similarities. This allows for more flexible and intelligent matching of queries to relevant information.
-- **Result Validation and Summarization:** Add a final LLM step to process to validate and summarize the search results. This filters out irrelevant information that might have been returned by the vector search, and synthesizes the relevant information into a coherent answer. You can also provide instructions for handling cases where no relevant information is found.
-
-This advanced technique addresses a key limitation of vector search: while vector search is excellent at finding semantically similar content, it always returns results, even if none are truly relevant. The validation step ensures that the final output is both relevant and accurate.
-
-By implementing this multi-step process, you can create AI tools capable of handling complex queries with high accuracy, even when dealing with ambiguous user inputs or incomplete knowledge bases. This reduces the risk of irrelevant or hallucinated responses.
diff --git a/build/knowledge/create-knowledge.mdx b/build/knowledge/create-knowledge.mdx
index 6bb13e45..87ca07d9 100644
--- a/build/knowledge/create-knowledge.mdx
+++ b/build/knowledge/create-knowledge.mdx
@@ -1,193 +1,66 @@
 ---
-title: "Knowledge"
-sidebarTitle: "Create knowledge"
-description: "Our Retrieval Augmented Generation (RAG) solution"
+title: "Create Knowledge"
+sidebarTitle: "Create Knowledge"
+description: "Create a Knowledge base and connect it to your Agents."
 ---
 
-# Create and Organize Knowledge
-
-This guide walks you through creating knowledge bases, organizing them, and connecting them to your agents. For an overview of what Knowledge is and how it works, see [Knowledge](/get-started/core-concepts/knowledge).
-
-## Creating Knowledge Sources
-
-Relevance AI offers multiple flexible approaches to create knowledge, accommodating various information types and sources:
-
-### Manual Input
-
-When you have specific information that isn't contained in existing documents, you can manually create and structure your knowledge:
-
-1. Navigate to the Knowledge section in your Relevance AI dashboard
-2. Click "Create Knowledge"
-3. Select "Empty Table" as your source
-4. Name your knowledge base
-5. Add columns to structure your information (e.g., Question, Answer, Category)
-6. Enter your information directly into the table
-7. Click "Create" to save your knowledge base
-
-This approach gives you complete control over the structure and content of your knowledge base, allowing you to create precisely tailored information resources.
-
-### Upload Documents
-
-When your information already exists in document form, you can quickly import it:
-
-1. Navigate to the Knowledge section
-2. Click "Create Knowledge"
-3. Select "Upload Files" as your source
-4. Choose the file(s) you want to upload (supported formats include CSV, PDF, Excel, JSON, and audio files)
-5. Configure parsing options if needed
-6. Name your knowledge base
-7. Click "Create" to process and import your documents
-
-Relevance AI automatically processes these documents, extracting the relevant information and making it searchable for your agents.
-
-### Extract Website Content
-
-To incorporate information from websites:
-
-1. Navigate to the Knowledge section
-2. Click "Create Knowledge"
-3. Select "Website" as your source
-4. Enter the URL(s) you want to extract content from
-5. Configure crawling options (depth, specific pages, etc.)
-6. Name your knowledge base
-7. Click "Create" to fetch and process the website content
-
-This method is perfect for incorporating information from your company website, documentation sites, or other online resources without manually copying information.
-
-### Connect Third-Party Integrations
-
-You can use third-party integrations as integrated Knowledge sources to ensure your Agents have access to the most current information across your entire technology stack. You can learn more about each of our supported integrated Knowledge sources below. 
-
-<Card title="Google Drive" href="/build/knowledge/integrated-knowledge-sources/google-drive" icon="google-drive">Use Google Drive as a source of Knowledge for your Agents</Card>
-
-<Card title="Sharepoint" href="/build/knowledge/integrated-knowledge-sources/sharepoint" icon="microsoft">Connect to Sharepoint as a source of Knowledge for your Agents</Card>
-
-<Card title="Notion" href="/build/knowledge/integrated-knowledge-sources/notion" icon="notion">Use Notion as a source of Knowledge for your Agents</Card>
-
-
-## Organizing Your Knowledge
-
-Effective knowledge organization is crucial for ensuring your agents can quickly find and use the right information. Here are strategies for organizing your knowledge in Relevance AI:
-
-### Structured Tables
-
-For FAQ-style knowledge or structured data:
-
-1. Create clear column headers that describe the information (e.g., "Question," "Answer," "Category")
-2. Use consistent formatting within each column
-3. Include metadata columns to help with filtering and organization
-4. Consider adding tags or categories to group related information
-
-### Document Chunking
-
-When importing documents:
-
-1. Configure appropriate chunking settings to break down large documents into manageable pieces
-2. Balance chunk size - too small may lose context, too large may dilute relevance
-3. Consider overlapping chunks to maintain context across sections
-4. Use metadata to maintain relationships between chunks from the same source
-
-### Knowledge Collections
-
-Group related knowledge bases into collections:
-
-1. Create separate knowledge bases for different domains or purposes
-2. Use consistent naming conventions for your knowledge bases
-3. Consider the scope of each knowledge base - more focused bases often yield more precise results
-4. Document the purpose and contents of each knowledge base for team reference
-
-## Enhancing Knowledge Quality
-
-To maximize the effectiveness of your knowledge bases:
-
-### Metadata Enrichment
-
-Add contextual metadata to your knowledge entries:
-
-1. Include creation and update dates to track freshness
-2. Add author information for accountability
-3. Tag entries with relevant categories or topics
-4. Include confidence scores or verification status where applicable
-
-### Knowledge Verification
-
-Implement processes to ensure accuracy:
-
-1. Regularly review and update your knowledge bases
-2. Set up workflows for subject matter experts to verify information
-3. Track usage patterns to identify frequently accessed or potentially problematic entries
-4. Implement version control for important knowledge bases
-
-### Semantic Organization
-
-Enhance retrievability with semantic approaches:
-
-1. Use consistent terminology throughout your knowledge bases
-2. Consider adding synonyms or alternative phrasings for important concepts
-3. Structure information in a question-answer format where appropriate
-4. Include examples and use cases to illustrate concepts
-
-## Connecting Knowledge to Agents
-
-Once your knowledge is created and organized, connect it to your agents:
-
-1. Navigate to your agent's configuration page
-2. Select "Add existing knowledge"
-3. Select the knowledge set you would like to add
-4. Select how the agent should use this knowledge
-   1. Add all to prompt: this option adds the entire knowledge set directly into the prompt every time the agent runs.
-      - _Best for small or simple data sets_
-      - _Easier to use with no extra configuration needed_
-   2. Allow agent to search: this uses Retrieval-Augmented Generation (RAG), where the agent searches the knowledge set using a tool.
-      - _Best for large or complex data sets_
-      - _More flexible and scalable_
-5. Depending on the option you chose, you can now see the name of your knowledge set as a  tool or knowledge set variable in your agent prompt.
-
-## Advanced Knowledge Configuration
-
-Fine-tune how your agents interact with knowledge:
-
-### Retrieval Settings
-
-Adjust how your agent searches for information:
-
-1. Configure the number of results returned for each query
-2. Set relevance thresholds to ensure only highly relevant information is used
-3. Adjust search algorithms between keyword-based and semantic approaches
-4. Configure whether the agent should use knowledge for all queries or only specific types
-
-### Knowledge Prioritization
-
-When using multiple knowledge bases:
-
-1. Set priority levels for different knowledge sources
-2. Configure fallback behavior when information isn't found in primary sources
-3. Set up rules for resolving conflicts between different knowledge sources
-4. Consider creating specialized knowledge bases for specific query types
-
-### Query Transformation
-
-Enhance retrieval effectiveness:
-
-1. Configure query preprocessing to improve match quality
-2. Set up query expansion to include related terms
-3. Implement query classification to route different types of questions to appropriate knowledge bases
-4. Use feedback loops to improve retrieval quality over time
-
-## Best Practices for Knowledge Management
-
-To maintain effective knowledge bases over time:
-
-1. **Regular Updates**: Schedule periodic reviews to keep information current
-2. **Version Control**: Track changes to your knowledge bases, especially for critical information
-3. **Usage Analytics**: Monitor how your agents use knowledge to identify gaps or improvement opportunities
-4. **Feedback Integration**: Create processes to incorporate user feedback into your knowledge bases
-5. **Documentation**: Maintain clear documentation about your knowledge structure and organization
-6. **Quality Control**: Implement validation processes for new knowledge entries
-7. **Scalable Structure**: Design your knowledge organization to accommodate growth
-
-## Related Features
-
-- [Access Knowledge](https://relevanceai.com/docs/build/knowledge/access-knowledge): Learn how to configure how your agents and tools access and use your knowledge bases.
-- [Enrich with Tool](https://relevanceai.com/docs/build/knowledge/enrich-with-tool): Discover how to enhance your knowledge bases with additional context using tools.
-- [Advanced Knowledge Retrieval](https://relevanceai.com/docs/build/knowledge/advanced-knowledge-retrieval): Explore advanced techniques for optimizing how your agents retrieve and use knowledge.
\ No newline at end of file
+This guide walks you through creating a Knowledge base and connecting it to an Agent. For an overview of what Knowledge is and how it works, see [Knowledge](/get-started/core-concepts/knowledge).
+
+## Ways to create Knowledge
+
+<CardGroup cols={2}>
+  <Card title="Empty table" icon="table">
+    Start from scratch and structure the data yourself — useful for FAQ-style or tabular content.
+  </Card>
+  <Card title="Upload files" icon="file-arrow-up">
+    Import CSV, PDF, Excel, JSON, or audio files. Relevance AI parses them into a searchable table.
+  </Card>
+  <Card title="Website" icon="globe">
+    Extract content from one or more URLs — handy for company sites and documentation.
+  </Card>
+  <Card title="Integrated source" icon="plug">
+    Sync from Google Drive, SharePoint, Notion, or Confluence so your Knowledge stays current.
+  </Card>
+</CardGroup>
+
+To create a Knowledge base, click **Knowledge** in the left sidebar, then **Create Knowledge**, and pick one of the options above.
+
+- **Empty table** — name the table and add columns (for example Question, Answer, Category), then enter rows directly.
+- **Upload files** — choose your file(s), confirm the parsing options, and name the table. Supported formats are CSV, PDF, Excel, JSON, and audio.
+- **Website** — enter the URL(s) to crawl and name the table.
+
+### Integrated Knowledge sources
+
+Connect a third-party source so your Agents always read the latest version of your documents. Each source has its own setup guide:
+
+<CardGroup cols={2}>
+  <Card title="Google Drive" href="/build/knowledge/integrated-knowledge-sources/google-drive" icon="google-drive">
+    Read selected Google Drive files as Knowledge.
+  </Card>
+  <Card title="SharePoint" href="/build/knowledge/integrated-knowledge-sources/sharepoint" icon="microsoft">
+    Read selected SharePoint files and folders as Knowledge.
+  </Card>
+  <Card title="Notion" href="/build/knowledge/integrated-knowledge-sources/notion" icon="notion">
+    Read selected Notion pages and databases as Knowledge.
+  </Card>
+  <Card title="Confluence" href="/build/knowledge/integrated-knowledge-sources/confluence" icon="confluence">
+    Read selected Confluence pages and spaces as Knowledge.
+  </Card>
+</CardGroup>
+
+## Connect Knowledge to an Agent
+
+1. Open your Agent and go to the **Build** screen.
+2. Click **Knowledge**, then **Add existing Knowledge**.
+3. Select the Knowledge set you want to add.
+4. Choose how the Agent should use it:
+   - **Add all to prompt** — includes the entire Knowledge set in the prompt every time the Agent runs. Best for small or simple datasets.
+   - **Allow agent to search** — the Agent searches the Knowledge set with RAG and pulls only what's relevant. Best for large or complex datasets.
+
+Depending on the option you choose, the Knowledge set appears in your prompt as a Knowledge variable or as a search Tool.
+
+## What's next?
+
+- [Enrich with a Tool](/build/knowledge/enrich-with-tool) — run a Tool across your table to add summaries, tags, or derived fields.
+- [Knowledge Tool steps](/build/knowledge/knowledge-tool-steps) — read from and write to Knowledge inside a Tool.
+- [Delete knowledge](/build/knowledge/delete-knowledge) — remove a Knowledge table when you no longer need it.
diff --git a/build/knowledge/delete-knowledge.mdx b/build/knowledge/delete-knowledge.mdx
new file mode 100644
index 00000000..53b669e9
--- /dev/null
+++ b/build/knowledge/delete-knowledge.mdx
@@ -0,0 +1,37 @@
+---
+title: "Delete Knowledge"
+sidebarTitle: "Delete Knowledge"
+description: "Delete a Knowledge table from your Relevance AI project."
+---
+
+This page covers deleting an entire Knowledge table from your project. To delete specific rows from inside a Tool, use the [Delete Knowledge Tool step](/build/knowledge/knowledge-tool-steps#delete-knowledge) instead.
+
+## How to delete a Knowledge table
+
+{/* TODO: Supademo recording of the delete flow */}
+
+1. Click **Knowledge** in the left sidebar of Relevance AI.
+2. Click the three dots button next to the Knowledge table you want to delete, then select **Delete**.
+3. On the pop-up that appears, click **Delete** to confirm.
+
+<Warning>
+Deleting a Knowledge table is permanent and cannot be undone. All rows, columns, and uploaded files in that table are removed, and any Agent or Tool that referenced it will no longer find it.
+</Warning>
+
+<Note>
+Knowledge tables on long-inactive, non-Enterprise accounts were subject to a [one-time cleanup](/build/knowledge/inactive-table-deletion). It was a single past event, not a recurring policy.
+</Note>
+
+## Frequently asked questions (FAQs)
+
+<AccordionGroup>
+  <Accordion title="Can I recover a deleted Knowledge table?">
+    No. Once a Knowledge table is deleted it cannot be recovered, and our support team cannot restore it. Export anything you want to keep before deleting.
+  </Accordion>
+  <Accordion title="What happens to Agents that used the deleted table?">
+    The Agent keeps running, but it can no longer retrieve from that table. Remove the Knowledge reference from the Agent or connect a different table.
+  </Accordion>
+  <Accordion title="How do I delete only some rows instead of the whole table?">
+    Use the [Delete Knowledge Tool step](/build/knowledge/knowledge-tool-steps#delete-knowledge) inside a Tool to delete rows that match a filter, leaving the rest of the table intact.
+  </Accordion>
+</AccordionGroup>
diff --git a/build/knowledge/enrich-with-tool.mdx b/build/knowledge/enrich-with-tool.mdx
index 189e5287..38adb3e5 100644
--- a/build/knowledge/enrich-with-tool.mdx
+++ b/build/knowledge/enrich-with-tool.mdx
@@ -28,8 +28,6 @@ There are two ways to start an enrichment on a Knowledge table.
     }}/>
 </div>
 
-{/* TODO: screenshot — Knowledge table with Enrich button highlighted */}
-
 1. Navigate to **Knowledge** and open the table you want to enrich.
 2. Click the **Enrich** button in the table toolbar.
 3. Select a Tool from the library.
diff --git a/build/knowledge/find-and-use-knowledge.mdx b/build/knowledge/find-and-use-knowledge.mdx
deleted file mode 100644
index 0e5fc49c..00000000
--- a/build/knowledge/find-and-use-knowledge.mdx
+++ /dev/null
@@ -1,199 +0,0 @@
----
-title: 'Find and Use Knowledge'
-sidebarTitle: 'Find and Use Knowledge'
-description: "Knowledge is the foundation of intelligent AI agents in Relevance AI."
----
-
-## Understanding Knowledge in Relevance AI
-
-Knowledge in Relevance AI refers to any information that your agents can access and reference when responding to queries or performing tasks. This information can come in various forms:
-
-- **Factual information** stored in knowledge bases
-- **Contextual examples** that demonstrate desired outputs
-- **External data sources** connected through integrations
-- **Website content** extracted from specific URLs
-
-Think of knowledge as the reference material your agents consult before formulating responses. Just as a human expert might refer to documentation, databases, or examples before answering a question, your AI agents can leverage knowledge to ground their responses in factual information.
-
-## Finding Knowledge
-
-There are several ways to find and access knowledge within Relevance AI:
-
-### Navigating to the Knowledge Section
-
-1. Log into your Relevance AI dashboard
-2. Click on "Knowledge" in the main navigation menu
-3. Browse existing knowledge bases or create new ones
-
-### Searching for Specific Knowledge
-
-Within the Knowledge section, you can:
-
-- Use the search bar to find specific knowledge bases by name or content
-- Filter knowledge bases by type, creation date, or other attributes
-- Sort knowledge bases to quickly locate what you need
-
-### Exploring Knowledge Categories
-
-Knowledge bases in Relevance AI are typically organized into categories based on their purpose:
-
-- **Reference Knowledge**: Comprehensive information repositories like FAQs, product details, or company policies
-
-- **Example Knowledge**: Samples of desired outputs that demonstrate "what good looks like"
-- **Procedural Knowledge**: Step-by-step instructions for completing specific tasks
-- **External Knowledge**: Information retrieved from integrated tools and services
-
-## Using Knowledge with Your Agents
-
-Once you've found the knowledge you need, there are several ways to use it with your agents:
-
-### Connecting Knowledge Bases to Agents
-
-1. Navigate to the agent you want to enhance
-2. Select "Knowledge" from the agent configuration options
-3. Choose the knowledge base(s) you want to connect
-4. Configure retrieval settings to determine how the agent accesses the knowledge
-
-### Providing Contextual Examples
-
-For tasks where you want to guide your agent's output style or format:
-
-1. Create a knowledge base with exemplary outputs
-2. Connect this knowledge base to your agent
-3. Include instructions that direct the agent to follow these examples
-
-For instance, if you want your agent to write case studies in a specific format, provide examples of well-crafted case studies in a knowledge base.
-
-### Leveraging Knowledge in Agent Prompts
-
-When designing agent prompts, you can explicitly instruct the agent to reference specific knowledge:
-
-> Before responding, please check the knowledge base for information about [specific topic].
-
-This ensures your agent actively seeks relevant information rather than relying solely on its pre-trained knowledge.
-
-## Knowledge Retrieval Methods
-
-Relevance AI offers several methods for retrieving knowledge:
-
-### Semantic Search
-
-Semantic search finds information based on meaning rather than exact keyword matches. This allows agents to retrieve relevant information even when queries use different terminology than what's in the knowledge base.
-
-To optimize for semantic search:
-
-- Structure your knowledge with clear, descriptive content
-- Include synonyms and alternative phrasings for important concepts
-
-- Organize related information together for better contextual understanding
-
-### Hybrid Search
-
-Hybrid search combines semantic search with keyword matching for more precise results. This is particularly useful when your knowledge base contains specific terminology or unique identifiers.
-
-### Filtered Retrieval
-
-You can set up filters to narrow down knowledge retrieval based on specific attributes:
-
-1. Navigate to the knowledge base settings
-2. Configure retrieval filters based on metadata fields
-3. Apply these filters to ensure agents only access relevant information
-
-## Knowledge Types and Their Uses
-
-Different types of knowledge serve different purposes:
-
-### Snippet Knowledge
-
-Small pieces of information that provide specific guidance or examples:
-
-- Use for: Style guides, tone examples, formatting templates
-- Best for: Shaping how agents respond rather than what they respond with
-- Example: "This is what a professional email response should look like..."
-
-### Database Knowledge
-
-Comprehensive collections of information organized in a structured format:
-
-- Use for: FAQs, product catalogs, support documentation
-- Best for: Providing detailed, factual information on a wide range of topics
-- Example: A table of product specifications and features
-
-### Integration Knowledge
-
-Information retrieved from external tools and services:
-
-- Use for: Real-time data, website content, third-party databases
-- Best for: Ensuring agents have access to the most current information
-- Example: Documentation pulled from your company website
-
-## Best Practices for Knowledge Management
-
-To get the most out of knowledge in Relevance AI:
-
-### Organize Knowledge Strategically
-
-- Create separate knowledge bases for different topics or departments
-- Use clear, descriptive names for easy identification
-- Add metadata to help with filtering and organization
-
-### Update Knowledge Regularly
-
-- Schedule regular reviews of your knowledge bases
-
-- Update information as products, policies, or procedures change
-- Remove outdated information to prevent confusion
-
-### Monitor Knowledge Usage
-
-- Review which knowledge bases are being accessed most frequently
-- Identify gaps where agents might need additional information
-- Refine knowledge based on actual usage patterns
-
-### Balance Comprehensiveness with Relevance
-
-- Include enough detail for accurate responses
-- Avoid overwhelming knowledge bases with unnecessary information
-- Focus on quality over quantity
-
-## Troubleshooting Knowledge Retrieval
-
-If your agents aren't effectively using knowledge:
-
-### Check Knowledge Connection
-
-Ensure the knowledge base is properly connected to the agent and that retrieval settings are configured correctly.
-
-### Review Knowledge Content
-
-Examine whether the knowledge base contains the information the agent needs in a format it can effectively use.
-
-### Adjust Retrieval Settings
-
-Modify search parameters, result limits, or relevance thresholds to improve retrieval accuracy.
-
-### Test with Sample Queries
-
-Use the testing interface to see how the agent retrieves and uses knowledge for specific questions.
-
-## Frequently asked questions (FAQs)
-
-**Q: How much knowledge can I add to my agents?**
-
-A: Relevance AI supports extensive knowledge bases, but for optimal performance, focus on providing relevant, well-structured information rather than simply maximizing volume.
-
-**Q: Can I use multiple knowledge bases with a single agent?**
-
-A: Yes, you can connect multiple knowledge bases to one agent. The agent will search across all connected knowledge bases when responding to queries.
-
-**Q: How do I know if my agent is using the knowledge effectively?**
-
-A: Use the agent testing interface to see which knowledge sources are being retrieved for specific queries. You can also review conversation logs to see how knowledge is being incorporated into responses.
-
-**Q: Can I prioritize certain knowledge over others?**
-
-A: Yes, you can configure retrieval settings to prioritize specific knowledge bases or types of information based on relevance scores or metadata attributes.
-
-**Q: What's the difference between knowledge and tools?**
-
-A: Knowledge provides information for agents to reference, while tools enable agents to perform actions or access external systems. Knowledge informs what agents know, while tools expand what agents can do.
\ No newline at end of file
diff --git a/build/knowledge/inactive-table-deletion.mdx b/build/knowledge/inactive-table-deletion.mdx
index 3e6d1bca..e6077132 100644
--- a/build/knowledge/inactive-table-deletion.mdx
+++ b/build/knowledge/inactive-table-deletion.mdx
@@ -18,7 +18,7 @@ Deletion of inactive Knowledge tables is permanent and cannot be undone. All dat
 
 Your account is considered inactive when **both** of the following conditions have been true for the last 182 days:
 
-- No tool or agent has been run
+- No Tool or Agent has been run
 - No login to the Relevance AI platform
 
 Both conditions must apply simultaneously. If either condition is not met — for example, if you have logged in within the last 182 days — your account is considered active and your Knowledge tables will not be deleted.
@@ -58,16 +58,16 @@ If you believe you received a deletion warning in error — for example, if you
     No. Once Knowledge tables are deleted, the data cannot be recovered. If you receive a warning email, log in and run an Agent or Tool before the 4-day window closes.
   </Accordion>
 
-  <Accordion title="What counts as 'running' a tool or agent?">
+  <Accordion title="What counts as 'running' a Tool or Agent?">
     Any execution of a Tool or Agent through the Relevance AI platform counts as activity. This includes manual runs as well as automated or scheduled runs.
   </Accordion>
 
   <Accordion title="How is inactivity measured?">
-    Inactivity is measured from two signals: the last tool or agent run, and the last login to the platform. Both must be absent for 182 consecutive days for your Knowledge tables to qualify for deletion in this one-time event. A single login or run within that window is sufficient to prevent it.
+    Inactivity is measured from two signals: the last Tool or Agent run, and the last login to the platform. Both must be absent for 182 consecutive days for your Knowledge tables to qualify for deletion in this one-time event. A single login or run within that window is sufficient to prevent it.
   </Accordion>
 
   <Accordion title="Is this related to the Enterprise Data Retention feature?">
-    No. These are two separate things. This one-time cleanup targets Knowledge tables on non-Enterprise accounts with 182 days of inactivity. The [Data Retention](/enterprise/data-retention) feature is an Enterprise-only configuration for managing the lifecycle of tool runs, agent conversations, and other activity data — it does not control Knowledge tables.
+    No. These are two separate things. This one-time cleanup targets Knowledge tables on non-Enterprise accounts with 182 days of inactivity. The [Data Retention](/enterprise/data-retention) feature is an Enterprise-only configuration for managing the lifecycle of Tool runs, Agent conversations, and other activity data — it does not control Knowledge tables.
   </Accordion>
 
   <Accordion title="Will my account be deleted?">
diff --git a/build/knowledge/integrated-knowledge-sources/confluence.mdx b/build/knowledge/integrated-knowledge-sources/confluence.mdx
new file mode 100644
index 00000000..1c075f9f
--- /dev/null
+++ b/build/knowledge/integrated-knowledge-sources/confluence.mdx
@@ -0,0 +1,37 @@
+---
+title: "Confluence as a Knowledge Source"
+sidebarTitle: "Confluence"
+description: "Use Confluence as a source of Knowledge for your Agents"
+---
+
+![Confluence as a source of Knowledge](/images/changelog/changelog-confluence.webp)
+
+Confluence can be added as an integrated Knowledge source via the Agent Builder for your Agents to read pages and use them as Knowledge.
+
+You can select specific Confluence pages or spaces for your Agent to read as Knowledge sources. When the source pages change, your Knowledge table updates automatically, so your Agents always reference the latest documentation.
+
+<Note>Confluence is also available as an integration for Tool steps. [Learn more about the Confluence integration](/integrations/popular-integrations/confluence).</Note>
+
+## Set up Confluence as a Knowledge source
+
+{/* TODO: Supademo recording of the Confluence knowledge setup */}
+
+To set up Confluence as a Knowledge source, first open an Agent and head to the Build screen. Then...
+
+1. Click 'Knowledge'
+2. Click 'Add Confluence'
+3. Select or connect the Confluence account you want to access
+4. Select the Confluence pages or spaces you wish to have the Agent read
+5. Once you've selected what you want to add as Knowledge, click 'Create'
+6. Choose how you want the Agent to use this Knowledge on the next screen
+
+## Frequently asked questions (FAQs)
+
+<AccordionGroup>
+  <Accordion title="Can I add a whole Confluence space, or only individual pages?">
+    You can select individual pages or an entire space. Selecting a space adds its pages as Knowledge.
+  </Accordion>
+  <Accordion title="Do changes in Confluence sync back to Relevance AI?">
+    Yes. When the content of a connected Confluence page changes, the Knowledge table updates automatically — you don't need to re-add the page.
+  </Accordion>
+</AccordionGroup>
diff --git a/build/knowledge/integrated-knowledge-sources/google-drive.mdx b/build/knowledge/integrated-knowledge-sources/google-drive.mdx
index 4c96ae15..e9e74c1b 100644
--- a/build/knowledge/integrated-knowledge-sources/google-drive.mdx
+++ b/build/knowledge/integrated-knowledge-sources/google-drive.mdx
@@ -31,12 +31,12 @@ To set up Google Drive as a Knowledge source, first, open an Agent up and head t
 
 <AccordionGroup>
   <Accordion title="Is there a file size limit for Google Drive files added to Knowledge?">
-    Yes, there is a limit of 50MB. If you try to select a file that exceeds the 50mb limit, you'll receive an error message indicating that the file is too large. To resolve this, you'll need to either compress the file to meet the size requirement or select a different file that is within the limit.
+    Yes. If you select a file that's too large, you'll get an error telling you so — compress the file or pick a smaller one. If you're unsure of the current limit, [contact support](/get-started/support).
   </Accordion>
-  <Accordion title="How often do agents fetch data from Google Drive?">
-    Agents automatically fetch data from the selected Google Drive files every 15 minutes. This ensures that your agents have access to the most up-to-date information available, helping them make informed decisions in real-time.
+  <Accordion title="How often do Agents fetch data from Google Drive?">
+    Connected Google Drive files sync automatically when their content changes, so your Agents reference the latest version without manual updates.
   </Accordion>
-  <Accordion title="What should I do if my agent fails to fetch data from Google Drive?">
+  <Accordion title="What should I do if my Agent fails to fetch data from Google Drive?">
     If your Agent fails to fetch data, you'll see an error notification indicating the failed fetch. You can check the specific file that caused the issue and ensure it's accessible and within the size limit. If the problem persists, try reconnecting your Google Drive or [reach out to support](/get-started/support).
   </Accordion>
 </AccordionGroup>
\ No newline at end of file
diff --git a/build/knowledge/integrated-knowledge-sources/notion.mdx b/build/knowledge/integrated-knowledge-sources/notion.mdx
index 4f0cd2c9..b307ccd1 100644
--- a/build/knowledge/integrated-knowledge-sources/notion.mdx
+++ b/build/knowledge/integrated-knowledge-sources/notion.mdx
@@ -30,7 +30,7 @@ To set up Notion as a Knowledge source, first, open an Agent up and head to the
   <Accordion title="Are Notion databases supported?">
     Yes! You can select both Notion pages and databases as Knowledge.
   </Accordion>
-  <Accordion title="How often do agents fetch data from Notion?">
-    Agents automatically fetch data from the selected Notion pages every 5 minutes. This ensures that your agents have access to the most up-to-date information available, helping them make informed decisions in real-time.
+  <Accordion title="How often do Agents fetch data from Notion?">
+    Connected Notion pages sync automatically when their content changes, so your Agents reference the latest version without manual updates.
   </Accordion>
 </AccordionGroup>
\ No newline at end of file
diff --git a/build/knowledge/integrated-knowledge-sources/sharepoint.mdx b/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
index 202c88c5..91ac4162 100644
--- a/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
+++ b/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
@@ -30,6 +30,6 @@ To set up Sharepoint as a Knowledge source, first, open an Agent up and head to
 
 <AccordionGroup>
   <Accordion title="Will any changes I make to my Sharepoint files be reflected in Relevance AI?">
-    Yes, our automatic content syncing feature ensures that any documents you upload initially, as well as any changes made to those files in SharePoint, are automatically updated in your agent's knowledge store. This means you won't have to worry about manually syncing files every time there's an update; it all happens seamlessly in the background.
+    Yes. Any documents you add initially, along with later changes made to those files in SharePoint, sync automatically to your Agent's Knowledge store. You don't need to manually re-sync files when something changes.
   </Accordion>
 </AccordionGroup>
\ No newline at end of file
diff --git a/build/knowledge/knowledge-tool-steps.mdx b/build/knowledge/knowledge-tool-steps.mdx
index 89d37c21..99452cb9 100644
--- a/build/knowledge/knowledge-tool-steps.mdx
+++ b/build/knowledge/knowledge-tool-steps.mdx
@@ -1,8 +1,434 @@
 ---
 title: 'Knowledge Tool steps'
-description: 'Use Tool steps to interact with your Knowledge tables'
+description: 'Use Tool steps to read from and write to your Knowledge tables inside a Tool'
 ---
 
-You can use Tool steps to interact with your Knowledge tables. 
+Knowledge Tool steps let a Tool read from and write to your knowledge tables. Use them to insert, upsert, update, delete, and retrieve rows, or to run semantic search over a knowledge set. Pick a step from the tabs below for its fields and examples.
 
-<Snippet file="components/integrations/knowledge-tool-steps.mdx" />
\ No newline at end of file
+## Writing knowledge
+
+These steps add, change, or remove rows in your knowledge table.
+
+<Tabs>
+  <Tab title="Insert knowledge" id="insert-knowledge" icon="circle-plus">
+    The Insert Knowledge step saves information by adding new rows to your knowledge table — useful for capturing and storing data dynamically as a Tool or agent runs.
+
+    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
+    <iframe src="https://app.supademo.com/embed/cmcskqz8x0dx09st8u6v0t5ka" frameBorder="0" title="Add the Insert Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **New data to insert** — a JSON array of objects, where each object is a row. Add more objects to insert multiple rows at once (see the examples below).
+    - **Sync on upload** — whether the data is vectorized when added. In most cases keep this on, so your agents can semantically search and retrieve the rows.
+
+    ### Formatting examples
+
+    <AccordionGroup>
+      <Accordion title="Insert a single row">
+```json
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Insert multiple rows">
+```json
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  },
+  {
+    "breed": "great dane",
+    "size": "large"
+  }
+]
+```
+Separate each object with a comma when inserting multiple rows.
+      </Accordion>
+    </AccordionGroup>
+
+    <Note>
+      When you wrap the Insert Knowledge step in a Tool for an agent to call, set the Tool input for the new data to the **JSON** input type (not Text), since the step expects a JSON array of objects. Optionally provide a JSON Schema matching your table's structure, and reference the input in the **New data to insert** field using variable mode (`{{input_variable_name}}`).
+    </Note>
+  </Tab>
+
+  <Tab title="Upsert knowledge" id="upsert-knowledge" icon="arrows-rotate">
+    The Upsert Knowledge step inserts new rows and updates existing ones in a single step, matching on an identifier field. Use it when you're syncing data that may or may not already exist — unlike Insert Knowledge, which always adds, and Update Knowledge, which only changes rows that already match.
+
+    ### Inputs
+
+    - **Identifier field** — the column used to match existing rows. A row whose identifier value already exists is updated; otherwise it's inserted as a new row.
+    - **Rows to upsert** — a JSON array of objects, where each object is a row. Each object should include the identifier field.
+    - **Sync on upload** — whether the data is vectorized on upsert. Keep this on so search stays accurate.
+
+    ### Formatting examples
+
+    <AccordionGroup>
+      <Accordion title="Upsert rows matched on 'breed'">
+```json
+// With identifier field set to "breed":
+// "poodle" is updated if it exists, "corgi" is inserted if it doesn't
+[
+  {
+    "breed": "poodle",
+    "size": "medium"
+  },
+  {
+    "breed": "corgi",
+    "size": "small"
+  }
+]
+```
+      </Accordion>
+    </AccordionGroup>
+  </Tab>
+
+  <Tab title="Update knowledge" id="update-knowledge" icon="pen-to-square">
+    The Update Knowledge step changes existing rows in your knowledge table, keeping your data current and accurate.
+
+    <div style={{ width:"95%",position:"relative",paddingTop:"62.5%" }}>
+    <iframe src="https://app.supademo.com/embed/cmcu7bc9z1pd69st851b05iwu" frameBorder="0" title="Add the Update Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **Filter condition** — `and` requires all conditions to match before a row is updated; `or` matches when any condition does. Only applies when the filter has more than one object.
+    - **Filters** — a JSON array of objects describing which rows to match.
+    - **Update value** — an object of new values. Each key matches a column name, and its value replaces the current value in matching rows.
+    - **Sync on upload** — whether the updated data is re-vectorized. Keep this on so search stays accurate.
+
+    ### Formatting examples
+
+    <AccordionGroup>
+      <Accordion title="Replace all poodles with bulldogs">
+```json
+// Filters
+[
+  {
+    "breed": "poodle"
+  }
+]
+```
+```json
+// Update value
+[
+  {
+    "breed": "bulldog"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Replace all small poodles with large bulldogs">
+```json
+// Filters
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  }
+]
+```
+```json
+// Update value
+[
+  {
+    "breed": "bulldog",
+    "size": "large"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Replace all poodles and bulldogs with cats">
+```json
+// Filters
+[
+  {
+    "breed": "poodle"
+  },
+  {
+    "breed": "bulldog"
+  }
+]
+```
+```json
+// Update value
+[
+  {
+    "breed": "cat"
+  }
+]
+```
+Separate each object with a comma when filtering multiple rows.
+      </Accordion>
+    </AccordionGroup>
+  </Tab>
+
+  <Tab title="Delete knowledge" id="delete-knowledge" icon="trash">
+    The Delete Knowledge step removes rows from your knowledge table, so you can keep your data relevant and up to date.
+
+    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
+    <iframe src="https://app.supademo.com/embed/cmcsl75ju0e0e9st8xzau7o3z?embed_v=2" frameBorder="0" title="Add the Delete Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **Filter condition** — `and` requires all conditions to match before a row is deleted; `or` matches when any condition does. Only applies when the filter has more than one object.
+    - **Filters** — a JSON array of objects describing which rows to delete.
+
+    <Warning>
+      Deletion is permanent. Every row matching the filter is removed, so test your filter with Get Knowledge first if you're unsure what it will match.
+    </Warning>
+
+    ### Formatting examples
+
+    <AccordionGroup>
+      <Accordion title="Delete all poodles">
+```json
+[
+  {
+    "breed": "poodle"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Delete all small poodles">
+```json
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Delete small poodles or any dog aged 4 (or)">
+```json
+// With filter condition set to "or"
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  },
+  {
+    "age": 4
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Delete only small poodles aged 4 (and)">
+```json
+// With filter condition set to "and"
+[
+  {
+    "breed": "poodle",
+    "size": "small"
+  },
+  {
+    "age": 4
+  }
+]
+```
+      </Accordion>
+    </AccordionGroup>
+  </Tab>
+</Tabs>
+
+## Searching and reading knowledge
+
+These steps retrieve rows by filter or rank them by relevance to a query.
+
+<Tabs>
+  <Tab title="Get knowledge" id="get-knowledge" icon="filter">
+    The Get Knowledge step retrieves rows directly from your knowledge table using filters, without RAG. Use it when you know which rows you want rather than searching by meaning.
+
+    <div style={{ width:"90%",position:"relative",paddingTop:"75%" }}>
+    <iframe src="https://app.supademo.com/embed/cmd2oyxum341oc4kj3skjizmf" frameBorder="0" title="Add the Get Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **Filter condition** — `and` requires all conditions to match before a row is returned; `or` matches when any condition does. Only applies when the filter has more than one object.
+    - **Filters** — a JSON array of objects describing which rows to retrieve.
+
+    ### Advanced
+
+    - **Fields to include** — the columns returned in the response. All fields are included by default. To target a specific field, prefix it with `data.` (for example, a `breed` field becomes `data.breed`).
+    - **Max records to return** — defaults to **20**.
+
+    ### Formatting examples
+
+    <AccordionGroup>
+      <Accordion title="Retrieve all large dogs">
+```json
+[
+  {
+    "size": "large"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Retrieve all large French Bulldogs">
+```json
+[
+  {
+    "breed": "French Bulldog",
+    "size": "large"
+  }
+]
+```
+      </Accordion>
+      <Accordion title="Retrieve all large French Bulldogs or small poodles (or)">
+```json
+// With filter condition set to "or"
+[
+  {
+    "size": "large",
+    "breed": "French Bulldog"
+  },
+  {
+    "size": "small",
+    "breed": "poodle"
+  }
+]
+```
+      </Accordion>
+    </AccordionGroup>
+  </Tab>
+
+  <Tab title="Knowledge search" id="knowledge-search" icon="magnifying-glass">
+    The Knowledge Search step searches a knowledge table with RAG and returns the most relevant rows for a query.
+
+    <div style={{ width:"90%",position:"relative",paddingTop:"55%" }}>
+    <iframe src="https://app.supademo.com/embed/cmd7198g26fevc4kjjsus430b?embed_v=2" frameBorder="0" title="Add the Knowledge Search tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **Query** — the text to search for.
+    - **Search type** — **Vector** finds results by meaning (semantic similarity), even when the exact words don't match; **Keyword** finds results by exact word match and is better for names and proper nouns.
+
+    ### Advanced
+
+    - **Output all fields** — when on, every field is returned including the similarity score; when off, only the content field is returned.
+    - **Max records to return** — the number of results to return (top k).
+    - **Similarity threshold** — the minimum score a result must reach to be returned. For vector search this is cosine similarity (0–1); for keyword search it's a BM25 score (0+). Raise it for fewer, more accurate results; lower it to be more inclusive.
+    - **Use exact search** — runs exact search (good for smaller knowledge sets) when on, or faster approximate search when off.
+    - **Filters** — restrict the search to a subset of rows, defined as JSON objects.
+
+    With the `exact_match` filter type, pass an array to `condition_value` to match any value in it (OR semantics). A single value (`"condition_value": "x"`) matches rows where the field equals x; an array (`"condition_value": ["a", "b"]`) matches rows where the field equals a or b.
+
+```json
+{
+  "field": "call_id",
+  "filter_type": "exact_match",
+  "condition": "==",
+  "condition_value": ["45eb244f-5008-4b7f-bfab-6f4db2189d2e", "4a678557-700e-407f-ab62-23d0decf1b52"]
+}
+```
+
+    This filter returns results where `call_id` matches either value.
+  </Tab>
+
+  <Tab title="Advanced knowledge search (2m)" id="advanced-knowledge-search-2m-context" icon="wand-magic-sparkles">
+    The Advanced Knowledge Search (2M context) step searches your knowledge table with a prompt using CAG (Cache Augmented Generation), loading your entire knowledge set into the model's long context window and generating an answer directly.
+
+    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
+    <iframe src="https://app.supademo.com/embed/cmcwogmal1l5n9emp09x9eqv7" frameBorder="0" title="Add the Advanced Knowledge Search (2m) Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
+
+    </div>
+
+    ### Inputs
+
+    - **Query** — the text to search for.
+    - **Knowledge source** — the set to search.
+    - **Gemini model** — the model used (currently two are available).
+
+    ### Advanced
+
+    - **System prompt** — the first message that instructs the model on its role, for example expert researcher, analyst, or tutor.
+    - **Temperature** — controls how creative or random the model's responses are. Lower is more focused; higher is more creative.
+    - **Enable grounding** — integrates Google Search results to inform and support the model's responses.
+    - **Max documents to search** — the number of documents retrieved from the knowledge set.
+  </Tab>
+</Tabs>
+
+## Using variables in JSON
+
+When building Tools with the Insert, Upsert, Update, Get, and Delete steps, you can pass data from earlier steps or user input into your knowledge operations. Reference a Tool input with `{{input_variable_name}}` or a previous step's output with `{{steps.step_name.output.variable_name}}`, and press the **{}** button beside any JSON input field to switch it to variable mode.
+
+Always wrap variables in quotes — `"{{variable_name}}"`. The final type is set by the column type in your knowledge table and converted to match on insert: a value bound for a number column becomes a number even though it's quoted, a text column keeps it as text, and a boolean column stores it as a boolean. Make sure your column types match the data you're storing.
+
+For example:
+
+<AccordionGroup>
+  <Accordion title="Using variables in filters">
+```json
+[
+  {
+    "breed": "{{user_breed_input}}",
+    "size": "{{user_size_input}}",
+    "age": "{{previous_step.output.age}}"
+  }
+]
+```
+  </Accordion>
+  <Accordion title="Using variables in data objects">
+```json
+[
+  {
+    "breed": "{{user_breed_input}}",
+    "size": "{{user_size_input}}",
+    "age": "{{user_age_input}}",
+    "weight": "{{previous_step.output.weight}}",
+    "is_active": "{{previous_step.output.is_active}}"
+  }
+]
+```
+  </Accordion>
+</AccordionGroup>
+
+<Note>
+  This quoting rule is specific to Knowledge Tool steps. In other Tool steps that accept JSON, `"{{variable}}"` is passed as a string while `{{variable}}` without quotes is passed as a number or boolean — the input box may flag a syntax error but still runs correctly.
+</Note>
+
+## Frequently asked questions (FAQs)
+
+<AccordionGroup>
+  <Accordion title="When should I use Upsert instead of Insert or Update?">
+    Upsert inserts new rows and updates existing ones in one step, matching on the identifier field. Use it when syncing data that may already exist. Use Insert when rows are always new, and Update when you only want to change rows that already match.
+  </Accordion>
+  <Accordion title="What happens if I don't enable 'Sync on upload'?">
+    The data is stored but not vectorized, so your agents can't semantically search or reference it until you vectorize it. This applies to the Insert, Upsert, and Update steps.
+  </Accordion>
+  <Accordion title="What data types can I write?">
+    Text, numbers, booleans, or any JSON-serializable value. Make sure each object in the array follows the correct formatting.
+  </Accordion>
+  <Accordion title="How do I update a field to be empty?">
+    Set the value to empty quote marks `""`.
+  </Accordion>
+  <Accordion title="When does the 'and' vs 'or' filter condition apply?">
+    Use `and` when all filter conditions must be true for a row to match; use `or` when any one of them can match. It only applies when the filter array has more than one object, and affects the Update, Delete, and Get steps.
+  </Accordion>
+  <Accordion title="What format should filters use?">
+    A JSON array of objects, where each object holds the field name and the value to filter by.
+  </Accordion>
+  <Accordion title="What if my filters don't match any rows?">
+    Nothing is deleted or returned. Make sure your filter values exactly match the data in the table, including casing and field names.
+  </Accordion>
+  <Accordion title="What's the difference between Get knowledge and Knowledge search?">
+    Get knowledge retrieves rows by exact filter match, without RAG. Knowledge search ranks rows by semantic or keyword relevance to a query. Use Get knowledge when you know the exact values to match, and Knowledge search when you want the most relevant results for a question.
+  </Accordion>
+  <Accordion title="What's the difference between Knowledge search and Advanced knowledge search (2m context)?">
+    Knowledge search runs RAG retrieval and returns the most relevant rows for a query, with control over search type, filters, and thresholds. Advanced knowledge search (2m context) loads your entire knowledge set into a long-context model and answers the query directly, which suits broad questions across the whole set. Start with Knowledge search for targeted retrieval.
+  </Accordion>
+</AccordionGroup>
diff --git a/build/knowledge/use-snippets-for-quick-access.mdx b/build/knowledge/use-snippets-for-quick-access.mdx
index 1e10a590..d8f8bb53 100644
--- a/build/knowledge/use-snippets-for-quick-access.mdx
+++ b/build/knowledge/use-snippets-for-quick-access.mdx
@@ -1,121 +1,42 @@
 ---
-title: 'Use Snippets for Quick Access'
+title: 'Use Snippets for quick access'
 sidebarTitle: 'Snippets'
-description: "Snippets transform how you manage shared text across your Relevance AI workspace."
+description: "Store reusable text once and reference it across your Tools and Agents."
 ---
 
-## Overview
+Snippets are named text variables you store once and reference anywhere a variable is accepted — Agent prompts, Tool inputs, and more. Update the Snippet in one place and every reference picks up the change, so shared text like a company name, support address, or standard disclaimer stays consistent.
 
- This powerful feature provides a centralized way to store and reference reusable text variables that can be used throughout your tools and agents. By creating a single source of truth for commonly used text elements, Snippets eliminate redundant updates and streamline your workflow.
+## Create a Snippet
 
-Whether you're managing company names, standard greetings, or complex message templates, Snippets make your text management more efficient and consistent across your entire AI ecosystem.
+1. Click **Snippets** in the left sidebar.
+2. Click **Create new Snippet**.
+3. Give it a descriptive name (for example `company_name` or `support_email`) and enter the text.
+4. Save.
 
-## Key Benefits
+## Reference a Snippet
 
-Snippets deliver several important advantages that enhance your workflow:
-
-- **Centralized Text Management** – Store common strings (company names, greetings, standard messages) in one accessible location.
-- **Universal Availability** – Use snippets anywhere a variable is accepted, including agents and tool inputs.
-- **Single-Source Updates** – Edit once and update everywhere, eliminating the need to manually change the same text across multiple tools.
-- **Simplified Architecture** – Eliminate 'prop-drilling' by making shared text easily accessible throughout your workspace.
-
-## How It Works
-
-Snippets integrate seamlessly into your existing workflow:
-
-1. **Define a Snippet**: Create a named text variable in the Snippets section.
-2. **Reference in Tools and Agents**: Use the `snippets.` prefix followed by your snippet name to reference it anywhere variables are accepted.
-3. **Update Centrally**: When you need to change the text, update it once in the Snippets section, and the change propagates everywhere it's used.
-
-For example, you can reference a snippet using this syntax: `{{ snippets.company_name }}`
-
-## Getting Started
-
-Accessing and using Snippets is straightforward:
-
-1. Navigate to the Snippets section in the left sidebar of your Relevance AI workspace
-2. Click "Create New Snippet"
-3. Provide a descriptive name and the text content for your snippet
-4. Save your snippet
-5. Reference your snippet in tools and agents using the `{{ snippets.your_snippet_name }}` syntax
-
-## Best Practices
-
-To get the most out of Snippets, consider these recommended practices:
-
-- **Use Descriptive Names**: Choose clear, intuitive names that indicate the snippet's purpose (e.g., `company_name`, `support_email`, `legal_disclaimer`).
-- **Categorize Related Snippets**: Use naming conventions to group related snippets (e.g., `email_header`, `email_signature`).
-- **Document Usage**: Add comments within your tools and agents to indicate where snippets are being used.
-- **Audit Regularly**: Periodically review your snippets to ensure they contain up-to-date information.
-- **Consider Scope**: Create snippets for text that appears in multiple places or might need updating across tools.
-
-## Use Cases
-
-Snippets are particularly valuable in these scenarios:
-
-- **Brand Consistency**: Maintain consistent company names, taglines, and messaging across all AI interactions.
-- **Contact Information**: Store email addresses, phone numbers, and URLs that might change over time.
-- **Standard Messages**: Create reusable templates for common responses, greetings, or disclaimers.
-- **Compliance Text**: Manage legal disclaimers, privacy statements, or terms of service that must be consistent.
-- **Personalization Elements**: Store reusable personalization templates that can be combined with dynamic data.
-
-## Implementation Examples
-
-### Example 1: Company Information
+Use the `snippets.` prefix with your Snippet name wherever variables are accepted:
 
 ```
-// Define snippets
-snippets.company_name = "Acme Corporation"
-snippets.support_email = "support@acmecorp.com"
-snippets.company_tagline = "Innovating for tomorrow, today."
-
-// Use in agent prompt
-"Thank you for contacting {{ snippets.company_name }}.
-Our mission is {{ snippets.company_tagline }}
-For additional support, please email {{ snippets.support_email }}."
-
+Thank you for contacting {{ snippets.company_name }}.
+For help, email {{ snippets.support_email }}.
 ```
 
-### Example 2: Email Templates
-
-```
-// Define snippets
-snippets.email_greeting = "Hello and thank you for reaching out,"
-snippets.email_signature = "Best regards,\\nThe Customer Success Team\\nAcme Corporation"
-
-// Use in email tool
-"{{ snippets.email_greeting }}
-
-[Personalized response goes here]
-
-{{ snippets.email_signature }}"
-
-```
-
-## Related Features
-
-[Agent Settings](https://relevanceai.com/docs/agent-settings) - Centralize your agent configurations for easier management, complementing snippets by providing a single source of truth for agent details.
-
-[Tool Version Control](https://relevanceai.com/docs/tool-version-control) - Save and track changes to your tools, working alongside snippets to create more maintainable and professional tool experiences.
+When you edit the snippet later, every place that references it updates automatically.
 
 ## Frequently asked questions (FAQs)
 
-**Q: Can snippets contain formatting like bold or italics?**
-
-A: Yes, snippets can contain Markdown formatting that will be rendered appropriately when used.
-
-**Q: Is there a size limit for snippets?**
-
-A: While there's no strict character limit, snippets are designed for reusable text elements rather than entire documents.
-
-**Q: Can I use variables within snippets?**
-
-A: Snippets are primarily for static text, but you can combine them with other variables in your tools and agents.
-
-**Q: How many snippets can I create?**
-
-A: There's no practical limit to the number of snippets you can create in your workspace.
-
-**Q: Can I organize snippets into folders or categories?**
-
-A: Currently, snippets are organized in a flat structure, but you can use naming conventions to create logical groupings.
\ No newline at end of file
+<AccordionGroup>
+  <Accordion title="Can Snippets contain Markdown formatting?">
+    Yes. Markdown in a Snippet renders when the Snippet is used.
+  </Accordion>
+  <Accordion title="Is there a size limit for Snippets?">
+    There's no strict character limit, but Snippets are meant for reusable text elements rather than entire documents.
+  </Accordion>
+  <Accordion title="Can I use variables inside a Snippet?">
+    Snippets are for static text. You can combine a Snippet with other variables in your Tools and Agents.
+  </Accordion>
+  <Accordion title="Can I organize Snippets into folders?">
+    Snippets are stored in a flat list. Use naming conventions (for example `email_header`, `email_signature`) to group related ones.
+  </Accordion>
+</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m.mdx b/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m.mdx
deleted file mode 100644
index 83ccf11b..00000000
--- a/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: "Advanced Knowledge Search (2m context)"
-description: "The 'Advanced Knowledge Search (2m context)' Tool allows you to search your knowledge table with a prompt using CAG"
----
-
-## Add the 'Advanced Knowledge Search (2m)' Tool step to your Tool
-
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-<iframe src="https://app.supademo.com/embed/cmcwogmal1l5n9emp09x9eqv7" frameBorder="0" title="Add the Advanced Knowledge Search (2m) Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-
-You can add the 'Advanced Knowledge Search (2m context) Tool' step to your Tool by:
-
-1. Creating a new Tool, then searching for the Advanced Knowledge Search (2m context) Tool step.
-2. Click "Expand" to see the full Tool step.
-3. Enter your search query in the **Query** field. 
-4. Select the knowledge source you would like to use.
-5. Select your Gemini model *(currently there are only 2 models available)*
-
-
-## Advanced settings
-
-### System prompt
-The system prompt is the very first message in a conversation that instructs the model on its role or the personality of the AI. Examples can be expert researcher, analyst or tutor.
-
-### Temperature
-The temperature setting controls how “creative” or “random” the model’s responses will be. Lower temperatures make the model more focused and deterministic, while higher temperatures make it more creative and unpredictable.
-
-### Enable Grounding
-Grounding integrates Google Search results to inform and support the model’s responses.
-
-### Page size
-Page size controls the number of documents that will be retrieved from the knowledge set.
-
diff --git a/build/tools/tool-steps/knowledge/advanced-knowledge-search.mdx b/build/tools/tool-steps/knowledge/advanced-knowledge-search.mdx
deleted file mode 100644
index dacd8edc..00000000
--- a/build/tools/tool-steps/knowledge/advanced-knowledge-search.mdx
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: "Advanced Knowledge Search"
-description: "The 'Advanced Knowledge Search' Tool allows for searching knowledge tables with a higher degree of accuracy and precision using RAG"
----
-
-## Add the 'Advanced Knowledge Search' Tool step to your Tool
-
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"55%" }}>
-<iframe src="https://app.supademo.com/embed/cmcycpn2u1bqnc4kjevlw5uy6" frameBorder="0" title="Add the Advanced Knowledge Search tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-You can add the' Advanced Knowledge Search' Tool step to your Tool by:
-
-1. Creating a new Tool, then searching for the Advanced Knowledge Search Tool step.
-2. Click "Expand" to see the full Tool step.
-3. Enter your search query in the **Query** field. 
-4. Select the search type:
-    - 	**Hybrid (recommended)**: Combines both semantic and keyword match for the most accurate and well-rounded results.
-    - 	**Vector**: Finds results based on meaning (semantic similarity). Great when you want answers even if the exact words don’t match.
-    - 	**Keyword**: Finds results based on exact word match. Useful when looking for specific terms or phrases.
-5. Select the Number of results to return. 
-6. Select the Knowledge set to use.
-7. Select the fields to vectorize - choose which columns from your data should be used for retrieval. **By default, all fields are included.**
-8. Select your retrieval postprocessing option after generating your answer: 
-    - 	**None**: No extra processing. You’ll get the raw retrieved text as-is.
-    -   **Basic**: Applies light formatting or cleaning to make the results easier to read.
-    -   **Summary**: Automatically summarizes the retrieved content to make it shorter and more digestible.
-    -   **Markdown**: Formats the retrieved text in Markdown (e.g., with bold, headings, lists) to improve readability or prep it for markdown-compatible interfaces.
-    -   **Entity Extraction**: Pulls out key information from the retrieved content, e.g., names, places, dates, etc.
-
-
-
-## Advanced settings
-
-### Post processing options
-
-<AccordionGroup>
-  <Accordion title="System prompt">
-    The system prompt is the very first message in a conversation that instructs the model on its role or the personality of the AI. Examples can be expert researcher, analyst or tutor.
-  </Accordion>
-
-  <Accordion title="Temperature">
-    The temperature setting controls how “creative” or “random” the model’s responses will be. Lower temperatures make the model more focused and deterministic, while higher temperatures make it more creative and unpredictable.
-  </Accordion>
-
-  <Accordion title="LLM model">
-    The model that will be used to generate the response. By default this model is `command-r-plus`.
-  </Accordion>
-</AccordionGroup>
-
-<Note>These options are only available if your have selected a post processing option in step 8</Note>
-
-### Vectoring Config
-<AccordionGroup>
-  <Accordion title="Embedding Model">
-    This is the model used to turn your text into a format the AI can understand and search through effectively. By default this model is `embed-english-v3.0`.
-
-    <Note>For multilingual support, you can use `embed-multilingual-v3.0`</Note>
-  </Accordion>
-
-  <Accordion title="Chunk Size">
-    Chunking size decides how much text is grouped together at once when the system processes your content. It’s measured in tokens, which are like small pieces of words. 
-    Common values are: `[128, 256, 512, 1024]`
-
-    <Tip>
-        - Larger chunks means more context and easier to understand the bigger picture—great for complex content whilst
-        - Smaller chunks means less context but more precise results—ideal for pinpointing specific information or short facts.
-    </Tip>
-  </Accordion>
-
-  <Accordion title="Chunking Strategy">
-            - **Base:** This is the standard chunking method. It simply splits your text into fixed-sized chunks without adding any extra context. It’s fast and works well for straightforward content.
-
-                <Tip>Best for: Clean, well-structured documents where each section makes sense on its own.</Tip>
-
-
-            - **Window:** This strategy adds some overlap between chunks, meaning parts of the text are repeated across neighboring chunks. This helps preserve context between sections.
-
-                <Tip>Best for: Text where ideas span multiple paragraphs—helps avoid losing important connections.</Tip>
-
-
-            - **Contextual:** This method intelligently adjusts how chunks are created based on the structure and meaning of the content. It uses more advanced logic to split text at natural breaks (like headings or sentences).
-
-                <Tip>Best for: Complex or unstructured content where preserving meaning and flow is important.</Tip>
-  </Accordion>
-</AccordionGroup>
-
-### Reranker Model
-Improves your search results by reordering them to show the most relevant information first. This is off by default but enabling it will boost performance in most cases.
-
-### Use Raw Files
-
-Select this if you want to run retrieval directly on the source file. 
-<Warning>This only works on PDF and PPTX files</Warning>
-
-### Update Vectors
-This option lets you force update the stored representations of your data (called embeddings) using your current settings—like a chunk size, embedding model, or chunking strategy.
-
-    #### Use Vision
-    If you have PDF files in your knowledge set, this option uses OCR (Optical Character Recognition) to re-extract the text from the raw PDF files. After OCR is applied, the system automatically triggers a vector update.
-    <Note>To enable Use Vision, Update Vectors must be set to true.</Note>  
-
-### Generate Citations
-
-Turn this on to include direct references from your knowledge set during retrieval.
-
-
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-    <Accordion title="What is the difference between Advanced Knowledge Search and Knowledge Search?">
-        - [Knowledge Search](/build/tools/tool-steps/knowledge/knowledge-search) is easier to use out of the box, with sensible default options that work well for most use cases.
-        -   Advanced Knowledge Search gives you greater control and fine-tuning capabilities for more precise retrieval — but may be slower in comparison. 
-        -   If you’re unsure which to choose, start with Knowledge Search.
-</Accordion>
-    <Accordion title="What is the difference between Advanced Knowledge Search and Advanced Knowledge Search (2m context)?">[Advanced Knowledge Search (2m context)](/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m) allows you to search your entire knowledge set with just a prompt whilst Advanced Knowledge Search allows you to filter down your search results for a more focused retrieval.</Accordion>
-    <Accordion title="When should I use Advanced Knowledge Search (2m) instead of the regular one?">Start with Advanced Knowledge Search (2m) for most use cases. It works best when you want quick, high-quality answers across your entire knowledge base without much setup. Switch to Advanced Knowledge Search when you need more control, such as filtering by specific fields or fine-tuning what gets retrieved.</Accordion>
-    <Accordion title="Which one gives better quality results?">Advanced knowledge search (2m) often produces richer, more complete answers, especially with large or unstructured content. However, Advanced Knowledge Search can give more precise results when you’re focused on a particular field, keyword, or structured dataset.</Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/delete-knowledge.mdx b/build/tools/tool-steps/knowledge/delete-knowledge.mdx
deleted file mode 100644
index 8b44f750..00000000
--- a/build/tools/tool-steps/knowledge/delete-knowledge.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: "Delete Knowledge"
-description: "The 'Delete Knowledge' Tool step allows your agent to remove information from your knowledge table — making it easy to manage and keep your data relevant and up to date."
----
-
----
-
-## Add the 'Delete Knowledge' Tool step to your Tool
-
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-<iframe src="https://app.supademo.com/embed/cmcsl75ju0e0e9st8xzau7o3z?embed_v=2" frameBorder="0" title="Add the Delete Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-You can add the 'Delete Knowledge' Tool step to your Tool by:
-
-1. Creating a new Tool, then clicking `+ Add Step`
-2. Searching for and adding the 'Delete Knowledge' Tool step
-3. Clicking ‘Expand’ to see the full Tool step
-4. Selecting the knowledge table you would like to access
-5. Filter condition: “and” vs “or” when matching data to delete:
-   - Use `and` when all specified conditions must match for a row to be deleted.
-   - Use `or` when any of the conditions can match.
-
-   <Note>
-     Filter condition only applies if you include more than one object in the filter
-   </Note>
-6. Filters: Accepts a JSON selection of objects, where each object corresponds to a row. Add more objects as outlined in the formatting examples below to delete multiple rows at once.
-7. Click `Run step` to test out the Tool
-
-## Common errors
-
-<Accordion title="Formatting issues">
-  This indicates that there is a formatting issue in the "Filters" input field. Make sure your object is formatted correctly. `Expected property name or '}' in JSON at...`
-</Accordion>
-
-<Accordion title="Incorrect data type">
-  This means the Filter being used is not a JSON. `Invalid JSON`
-</Accordion>
-
-## Formatting Examples
-
-### Example 1: Delete single condition
-
-```json
-// All poodles will be deleted
-[
-  {
-    "breed": "poodle"
-  }
-]
-```
-
-### Example 2: Delete single condition
-
-```json
-// All small poodles will be deleted
-[
-  {
-    "breed": "poodle",
-	"size": "small"
-  }
-]
-```
-
-### Example 3: Delete multiple conditions (_or_)
-
-```json
-// All small poodles will be deleted AND any dog aged 4 will be deleted
-[
-  {
-    "breed": "poodle",
-    "size": "small"
-  }, 
-  {
-    "age": 4
-  }
-]
-```
-
-### Example 3: Delete multiple conditions (_and_)
-
-```json
-// Only small poodles that are aged 4 will be deleted
-[
-  {
-    "breed": "poodle",
-    "size": "small"
-  }, 
-  {
-    "age": 4
-  }
-]
-```
-
-<Note>
-  Ensure to separate each object with a comma if inserting multiple rows.
-</Note>
-
-## Using Variables in JSON
-
-You can use variables from Tool inputs and other Tool steps in the **Filters** field. For detailed information on how to use variables in JSON for Knowledge Tool steps, including variable syntax and typing, see [Using Variables in JSON](/build/tools/tool-steps/knowledge/using-variables-in-json).
-
-For Knowledge Tool steps, all variables should be wrapped in quotes in the JSON format: `"{{variable_name}}"`. The filter values will be matched against your knowledge table data based on the column types.
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-    <Accordion title="What's the difference between using 'AND' and 'OR'?">
-        - Use **AND** when _all_ filter conditions must be true for a row to be deleted.
-        - Use **OR** when _any_ one of the conditions can match.
-
-        <Note>
-          This only applies when you include more than one object in the filter array. 
-        </Note>
-    </Accordion>
-    <Accordion title="Can I delete multiple rows at once?">
-        Yes. Any row that matches the filter condition you have specified will be deleted.
-    </Accordion>
-    <Accordion title="What if my filters don't match any rows?">
-        If no rows match the provided conditions, no data will be deleted. Make sure your filter values exactly match the data in the knowledge set (e.g., casing, field names, etc.).
-    </Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/get-knowledge.mdx b/build/tools/tool-steps/knowledge/get-knowledge.mdx
deleted file mode 100644
index 76d7605c..00000000
--- a/build/tools/tool-steps/knowledge/get-knowledge.mdx
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: "Get Knowledge"
-description: "The Get Knowledge feature allows you to search and retrieve information directly from your knowledge table without RAG"
----
-
-## Add the ‘Get Knowledge’ Tool step to your Tool
-
-<div style={{ width:"90%",position:"relative",paddingTop:"75%" }}>
-<iframe src="https://app.supademo.com/embed/cmd2oyxum341oc4kj3skjizmf" frameBorder="0" title="Add the Get Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-
-You can add the Get Knowledge’ Tool step to your Tool by:
-
-1. Creating a new Tool, then clicking `+ Add Step`
-2. Searching for and addingthe ‘Get Knowledge’ Tool step
-3. Clicking ‘Expand’ to see the full Tool step
-4. Selecting the Knowledge table you would like to access
-5. Filter condition: “and” vs “or” when matching data to update:
-   - Use **and** when all specified conditions must match for a row to be deleted.
-   - Use **or** when any of the conditions can match.
-   <Note>
-     Filter condition only applies if you include more than one object in the filter
-   </Note>
-6. Filters: Accepts a JSON selection of objects, where each object corresponds to a row. Add more objects as outlined in the formatting examples below to delete multiple rows at once.
-7. Click `Run step` to test out the Tool
-
-## Advanced settings
-
-### Fields to include
-
-This is the fields (columns) that will be included in the response. By default, all fields are included.
-
-<Tip> When targeting a specific field, you will need to prefix each field with `data.`. For example, if you have a field name `breed`, you will instead use `data.breed`. </Tip>
-
-### Number of records to retrieve
-
-This is the number of records to retrieve. By default, **20** records are retrieved.
-
-## Common errors
-<AccordionGroup>
-  <Accordion title="Formatting issues">
-    This indicates that there is a formatting issue in the "New data to insert" input field. Make sure your object is formatted correctly. `Expected property name or '}' in JSON at...`
-  </Accordion>
-
-  <Accordion title="Incorrect data type">
-    This means the data being inserted into the knowledge table is not a JSON. `Invalid JSON`
-  </Accordion>
-</AccordionGroup>
-
-## Formatting Examples
-
-### Example 1: Retrieve all large dogs
-
-```json
-[
-  {
-    "size": "large"
-  }
-]
-```
-
-### Example 2: Retrieve all large French Bulldogs
-
-```json
-[
-  {
-    "breed": "French Bulldog",
-    "size": "large"
-  },
-]
-```
-
-### Example 3: Retrieve all large dogs OR small poodles
-```json
-[
-  {
-    "size": "large",
-    "breed": "French Bulldog"
-  },
-  {
-    "size": "small",
-    "breed": "poodle"
-  }
-]
-```
-
-
-<Note>
-  Ensure to separate each object with a comma if inserting multiple rows.
-</Note>
-
-## Using Variables in JSON
-
-You can use variables from Tool inputs and other Tool steps in the **Filters** field. For detailed information on how to use variables in JSON for Knowledge Tool steps, including variable syntax and typing, see [Using Variables in JSON](/build/tools/tool-steps/knowledge/using-variables-in-json).
-
-For Knowledge Tool steps, all variables should be wrapped in quotes in the JSON format: `"{{variable_name}}"`. The filter values will be matched against your knowledge table data based on the column types.
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-    <Accordion title="What is the difference between get knowledge and advanced knowledge search?">
-        Get knowledge allows you to search and retrieve information directly from your knowledge table without RAG.
-    </Accordion>
-    <Accordion title="What format should I use for the filter?">
-        The filter should be a JSON array of objects. Each object should have the field name and the value you want to filter by.
-    </Accordion>
-    <Accordion title="What's the difference between using 'AND' and 'OR'?">
-        - Use **AND** when _all_ filter conditions must be true for a row to be retrieved.
-        - Use **OR** when _any_ one of the conditions can match.
-
-        <Note>
-          This only applies when you include more than one object in the filter array. 
-        </Note>
-    </Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/insert-knowledge.mdx b/build/tools/tool-steps/knowledge/insert-knowledge.mdx
deleted file mode 100644
index 3f5e5677..00000000
--- a/build/tools/tool-steps/knowledge/insert-knowledge.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-title: "Insert Knowledge"
-description: "The 'Insert Knowledge' Tool step lets your agent save information by adding new rows to your knowledge table—making it easy to capture and store data dynamically."
----
-
-## Add the 'Insert Knowledge' Tool step to your Tool
-
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-<iframe src="https://app.supademo.com/embed/cmcskqz8x0dx09st8u6v0t5ka" frameBorder="0" title="Add the Insert Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-
-You can add the 'Insert Knowledge' Tool step to your Tool by:
-
-1. Creating a new Tool, then clicking `+ Add Step`
-2. Searching for and adding the 'Insert Knowledge' Tool step
-3. Clicking 'Expand' to see the full Tool step
-4. Selecting the Knowledge table you would like to access
-5. New data to insert: Accepts a JSON selection of objects, where each object corresponds to a row. Add more objects as outlined in the formatting examples below to insert multiple rows at once.
-6. Use the **Sync on upload** field to determine whether the data should be vectorized when added to the knowledge set. In most cases, you'll want this enabled as it allows your agents to semantically search and retrieve relevant information from your knowledge table.
-7. Click `Run step` to test out the Tool
-
-## Common errors
-
-<Accordion title="Formatting issues">
-  This indicates that there is a formatting issue in the "New data to insert" input field. Make sure your object is formatted correctly. `Expected property name or '}' in JSON at...`
-</Accordion>
-
-<Accordion title="Incorrect data type">
-  This means the data being inserted into the knowledge table is not a JSON. `Invalid JSON`
-</Accordion>
-
-<Accordion title="Tool input type mismatch">
-  When creating a Tool that wraps the Insert Knowledge Tool step for use with AI agents, ensure the Tool input for new data is configured as a **JSON input type** rather than a Text input. The Insert Knowledge Tool step expects a JSON array of objects (as shown in the formatting examples above), so the Tool input should match this format to properly pass data from agents to the step.
-  
-  When setting up the Tool input:
-  - Use the **JSON** input type (not Text)
-  - Optionally provide a JSON Schema that matches the structure of your knowledge table to guide agents on the expected format
-  - Reference the Tool input variable in the Insert Knowledge Tool step's **New data to insert** field using variable mode (`{{input_variable_name}}`)
-  
-  This ensures that the data format passed from the Tool input to the Tool step remains consistent and properly structured.
-</Accordion>
-
-## Formatting Examples
-
-### Example 1: Insert single row
-
-```json
-[
-  {
-    "breed": "poodle",
-    "size": "small"
-  }
-]
-```
-
-### Example 2: Insert multiple rows
-
-```json
-[
-  {
-    "breed": "poodle",
-    "size": "small"
-  }, 
-  {
-    "breed": "great dane",
-    "size": "large"
-  }
-]
-```
-
-<Note>
-  Ensure to separate each object with a comma if inserting multiple rows.
-</Note>
-
-## Using Variables in JSON
-
-You can use variables from Tool inputs and other Tool steps in the **New data to insert** field. For detailed information on how to use variables in JSON for Knowledge Tool steps, including variable syntax and typing, see [Using Variables in JSON](/build/tools/tool-steps/knowledge/using-variables-in-json).
-
-For Knowledge Tool steps, all variables should be wrapped in quotes in the JSON format: `"{{variable_name}}"`. The type of the inserted value is determined by the column type defined in your knowledge table.
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-    <Accordion title="What happens if I don't enable 'Sync on Upload'?">
-        If "Sync on Upload" is disabled, the data will be stored but not vectorized. This means your agents won't be able to semantically search or reference that data until you manually vectorize it.
-    </Accordion>
-    <Accordion title="Can I update or delete rows later?">
-        Yes. After inserting data, you can manage your knowledge set using the available tools this includes updating or deleting rows as needed.
-    </Accordion>
-    <Accordion title="What data types can I insert?">
-        You can insert text, numbers, booleans, or any JSON-serializable value. Just make sure each object in the array follows the correct formatting.
-    </Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/knowledge-search.mdx b/build/tools/tool-steps/knowledge/knowledge-search.mdx
deleted file mode 100644
index 956be78e..00000000
--- a/build/tools/tool-steps/knowledge/knowledge-search.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: "Knowledge Search"
-description: "The 'Knowledge Search' Tool allows you to search knowledge tables with RAG"
----
-
-## Add the 'Knowledge Search' Tool step to your Tool
-
-<div style={{ width:"90%",position:"relative",paddingTop:"55%" }}>
-<iframe src="https://app.supademo.com/embed/cmd7198g26fevc4kjjsus430b?embed_v=2" frameBorder="0" title="Add the Knowledge Search tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-You can add the 'Knowledge Search' Tool step to your Tool by:
-
-1.  Creating a new Tool, then searching for the Knowledge Search Tool step.
-2.  Click "Expand" to see the full Tool step.
-3.  Select the Knowledge set to use.
-4.  Enter your search query in the **Query** field.
-5.  Select the search type:
-    -     **Vector**: Finds results based on meaning (semantic similarity). Great when you want answers even if the exact words don’t match.
-    -     **Keyword**: Finds results based on exact word match. Useful when looking for specific terms or phrases.
-
-## Advanced Settings
-
-### Vector field
-
-The vector field is the column used for searching your knowledge set using semantic similarity. By default, all fields are included unless you choose specific ones.
-
-### Output all fields
-
-- When enabled, all fields from your knowledge set will be shown - including the similarity score.
-- When disabled, only the main content field is returned.
-
-### Page size
-
-The number of results to return.
-
-### Similarity threshold
-
-All results are given a score between 0 and 1 based on how similar the result is to your query. This threshold is the minimum score for a result to be returned.
-
-<Tip>
-  Increase this value to get fewer but more accurate results. Lower it to be
-  more inclusive.
-</Tip>
-
-### Raw filters
-
-If you want to filter your search to a specific subset of entries in your knowledge set, you can use raw filters. Filters are defined as JSON objects.
-
-**OR Logic with Arrays:** When using `exact_match` filter type, you can pass an array to the `condition_value` field to create OR semantics. This allows you to match records where the field equals ANY value in the array.
-
-**Examples:**
-- Single value: `"condition_value": "x"` → matches records where field equals x
-- Array value: `"condition_value": ["a", "b"]` → matches records where field equals a OR b
-
-**Example filter with OR logic:**
-```json
-{
-  "field": "call_id",
-  "filter_type": "exact_match",
-  "condition": "==",
-  "condition_value": ["45eb244f-5008-4b7f-bfab-6f4db2189d2e", "4a678557-700e-407f-ab62-23d0decf1b52"]
-}
-```
-
-This filter will return results where `call_id` matches either of the two provided values.
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-  <Accordion title="What is the difference between Knowledge Search and Advanced Knowledge Search?">
-    - Knowledge Search is easier to use out of the box, with sensible default
-    options that work well for most use cases. - [Advanced Knowledge
-    Search](/build/tools/tool-steps/knowledge/advanced-knowledge-search) gives you
-    greater control and fine-tuning capabilities for more precise retrieval —
-    but may be slower in comparison.
-  </Accordion>
-  <Accordion title="When should I use Advanced Knowledge Search instead of the regular one?">
-    - If you’re unsure which to choose, start with Knowledge Search. - Knowledge
-    search works better out of the box, whilst advanced knowledge search gives
-    you more control and fine-tuning options.
-  </Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/update-knowledge.mdx b/build/tools/tool-steps/knowledge/update-knowledge.mdx
deleted file mode 100644
index 34439287..00000000
--- a/build/tools/tool-steps/knowledge/update-knowledge.mdx
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: "Update Knowledge"
-description: "The 'Update Knowledge' Tool step lets you update existing rows in your knowledge table—making it easy to keep your data current and accurate."
----
-
-## Add the 'Update Knowledge' Tool step to your Tool
-
-<div style={{ width:"95%",position:"relative",paddingTop:"62.5%" }}>
-<iframe src="https://app.supademo.com/embed/cmcu7bc9z1pd69st851b05iwu" frameBorder="0" title="Add the Update Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-</div>
-
-
-
-You can add the 'Update Knowledge' Tool step to your Tool by:
-
-1. Creating a new Tool, then clicking `+ Add Step`
-2. Searching for and adding the 'Update Knowledge' Tool step
-3. Clicking 'Expand' to see the full Tool step
-4. Selecting the knowledge table you would like to access
-5. Filter condition: "and" vs "or" when matching data to update:
-   - Use `and` when all specified conditions must match for a row to be updated.
-   - Use `or` when any of the conditions can match.
-   <Note>
-     Filter condition only applies if you include more than one object in the filter
-   </Note>
-6. Filters: Accepts a JSON selection of objects, where each object corresponds to a row. Add more objects as outlined in the formatting examples below to match multiple rows at once.
-7. Update value: Provide an object with the new values to update. Each key should match a column name in your knowledge table, and its corresponding value will replace the current value in the matching row.
-8. Use the **Sync on upload** field to determine whether the data should be vectorized when added to the knowledge set. In most cases, you'll want this enabled as it allows your agents to semantically search and retrieve relevant information from your knowledge table.
-9. Click `Run step` to test out the Tool
-
-
-## Common errors
-
-<Accordion title="Formatting issues">
-  This indicates that there is a formatting issue in the "New data to insert" input field. Make sure your object is formatted correctly. `Expected property name or '}' in JSON at...`
-</Accordion>
-
-<Accordion title="Incorrect data type">
-  This means the data being inserted into the knowledge table is not a JSON. `Invalid JSON`
-</Accordion>
-
-## Formatting Examples
-
-### Example 1: Replace all poodles with bulldogs
-
-```json
-// Filters
-[
-  {
-    "breed": "poodle"
-  }
-]
-```
-
-```json
-// Update value
-[
-  {
-    "breed": "bulldog"
-  }
-]
-```
-
-### Example 2: Replace all small poodles with large bulldogs
-
-```json
-// Filters
-[
-  {
-    "breed": "poodle",
-    "size": "small"
-  }
-]
-```
-
-```json
-// Update value
-[
-  {
-    "breed": "bulldog",
-    "size": "large"
-  }
-]
-```
-
-
-### Example 3: Replace all poodles *and* bulldogs with cats
-
-```json
-// Filters
-[
-  {
-    "breed": "poodle"
-  },
-  {
-    "breed": "bulldog"
-  }
-]
-```
-
-```json
-// Update value
-[
-  {
-    "breed": "cat"
-  }
-]
-```
-
-<Note>
-  Ensure to separate each object with a comma if filtering multiple rows.
-</Note>
-
-## Using Variables in JSON
-
-You can use variables from Tool inputs and other Tool steps in the **Filters** and **Update value** fields. For detailed information on how to use variables in JSON for Knowledge Tool steps, including variable syntax and typing, see [Using Variables in JSON](/build/tools/tool-steps/knowledge/using-variables-in-json).
-
-For Knowledge Tool steps, all variables should be wrapped in quotes in the JSON format: `"{{variable_name}}"`. The type of the updated value is determined by the column type defined in your knowledge table, and values will be automatically converted to match the column type during the update.
-
-## Frequently asked questions (FAQs)
-
-<AccordionGroup>
-    <Accordion title="What happens if I don't enable 'Sync on Upload'?">
-        If "Sync on Upload" is disabled, the data will be stored but not vectorized. This means your agents won't be able to semantically search or reference that data until you manually vectorize it.
-    </Accordion>
-    <Accordion title="How do I update a field to be empty/blank?">
-        You can update a field to be empty/blank by setting the value to empty quote marks `""`.
-    </Accordion>
-    <Accordion title="What data types can I update with?">
-        You can use text, numbers, booleans, or any JSON-serializable value. Just make sure each object in the array follows the correct formatting.
-    </Accordion>
-</AccordionGroup>
diff --git a/build/tools/tool-steps/knowledge/using-variables-in-json.mdx b/build/tools/tool-steps/knowledge/using-variables-in-json.mdx
deleted file mode 100644
index 8827d9ba..00000000
--- a/build/tools/tool-steps/knowledge/using-variables-in-json.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: "Using Variables in JSON"
-description: "Learn how to use variables from Tool inputs and other Tool steps in JSON fields for Knowledge Tool steps"
----
-
-When building Tools with Knowledge Tool steps (Insert, Update, Get, Delete Knowledge), you can reference inputs from Tool inputs or outputs from other Tool steps using variable syntax `{{variable_name}}`. This allows you to dynamically insert data from previous steps or user inputs into your knowledge operations.
-
-## Variable Syntax
-
-You can reference:
-- **Tool inputs**: `{{input_variable_name}}`
-- **Previous Tool step outputs**: `{{steps.step_name.output.variable_name}}`
-
-Press the **{}** button next to any JSON input field to switch to variable mode and reference these values.
-
-## Variable Typing for Knowledge Tool Steps
-
-For Knowledge Tool steps (Insert, Update, Get, Delete), **all variables should be wrapped in quotes** in the JSON format: `"{{variable_name}}"`. 
-
-The type of the inserted value is determined by the column type defined in your knowledge table. The system will automatically convert the value to match the column type during insertion.
-
-Make sure the column types in your knowledge table match the data types you want to store:
-- **Number columns**: Values will be converted to numbers on insert, even though they're quoted in the JSON
-- **Text/String columns**: Values will be stored as text
-- **Boolean columns**: Values will be stored as booleans
-
-## Examples
-
-### Example: Using Variables in Filters
-
-```json
-[
-  {
-    "breed": "{{user_breed_input}}",
-    "size": "{{user_size_input}}",
-    "age": "{{previous_step.output.age}}"
-  }
-]
-```
-
-### Example: Using Variables in Data Objects
-
-```json
-[
-  {
-    "breed": "{{user_breed_input}}",
-    "size": "{{user_size_input}}",
-    "age": "{{user_age_input}}",
-    "weight": "{{previous_step.output.weight}}",
-    "is_active": "{{previous_step.output.is_active}}"
-  }
-]
-```
-
-In these examples, all variables are wrapped in quotes as required for Knowledge Tool steps. The final type depends on your knowledge table column types:
-- If the `breed` and `size` columns are text columns, the values will be inserted as strings
-- If the `age` and `weight` columns are number columns, the values will be converted to numbers on insert, even though they're quoted in the JSON
-- The `is_active` column type determines whether the value is stored as a boolean
-
-## Variable Typing for Other Tool Steps
-
-**Note**: When passing values to other Tool steps that accept JSON input (not Knowledge Tool steps), the typing works differently:
-- `"{{variable}}"` will be passed as a string
-- `{{variable}}` (without quotes) will be passed as a number or boolean. The JSON input box may show a syntax error, but it will still run correctly.
-
-## See Also
-
-- [Insert Knowledge](/build/tools/tool-steps/knowledge/insert-knowledge)
-- [Update Knowledge](/build/tools/tool-steps/knowledge/update-knowledge)
-- [Get Knowledge](/build/tools/tool-steps/knowledge/get-knowledge)
-- [Delete Knowledge](/build/tools/tool-steps/knowledge/delete-knowledge)
-
diff --git a/docs.json b/docs.json
index 3056a6bd..032c28f1 100644
--- a/docs.json
+++ b/docs.json
@@ -208,18 +208,6 @@
                           "build/tools/tool-steps/llms/llm-tool-step"
                         ]
                       },
-                      {
-                        "group": "Knowledge Tool Steps",
-                        "pages": [
-                          "build/tools/tool-steps/knowledge/insert-knowledge",
-                          "build/tools/tool-steps/knowledge/delete-knowledge",
-                          "build/tools/tool-steps/knowledge/update-knowledge",
-                          "build/tools/tool-steps/knowledge/advanced-knowledge-search-2m",
-                          "build/tools/tool-steps/knowledge/knowledge-search",
-                          "build/tools/tool-steps/knowledge/get-knowledge",
-                          "build/tools/tool-steps/knowledge/using-variables-in-json"
-                        ]
-                      },
                       {
                         "group": "Confluence Tool Steps",
                         "pages": [
@@ -368,17 +356,22 @@
                 "pages": [
                   "build/knowledge/create-knowledge",
                   {
-                    "group": "Integrated Knowledge Sources",
+                    "group": "Build with Knowledge",
                     "pages": [
-                      "build/knowledge/integrated-knowledge-sources/google-drive",
-                      "build/knowledge/integrated-knowledge-sources/sharepoint",
-                      "build/knowledge/integrated-knowledge-sources/notion"
+                      "build/knowledge/knowledge-tool-steps",
+                      "build/knowledge/enrich-with-tool",
+                      {
+                        "group": "Knowledge Sources",
+                        "pages": [
+                          "build/knowledge/integrated-knowledge-sources/google-drive",
+                          "build/knowledge/integrated-knowledge-sources/sharepoint",
+                          "build/knowledge/integrated-knowledge-sources/notion",
+                          "build/knowledge/integrated-knowledge-sources/confluence"
+                        ]
+                      }
                     ]
                   },
-                  "build/knowledge/find-and-use-knowledge",
-                  "build/knowledge/enrich-with-tool",
-                  "build/knowledge/inactive-table-deletion",
-                  "build/knowledge/knowledge-tool-steps",
+                  "build/knowledge/delete-knowledge",
                   "build/knowledge/use-snippets-for-quick-access"
                 ]
               }
@@ -774,6 +767,38 @@
     }
   },
   "redirects": [
+    {
+      "source": "/build/tools/tool-steps/knowledge/insert-knowledge",
+      "destination": "/build/knowledge/knowledge-tool-steps#insert-knowledge"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/update-knowledge",
+      "destination": "/build/knowledge/knowledge-tool-steps#update-knowledge"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/delete-knowledge",
+      "destination": "/build/knowledge/knowledge-tool-steps#delete-knowledge"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/get-knowledge",
+      "destination": "/build/knowledge/knowledge-tool-steps#get-knowledge"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/knowledge-search",
+      "destination": "/build/knowledge/knowledge-tool-steps#knowledge-search"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/advanced-knowledge-search",
+      "destination": "/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/advanced-knowledge-search-2m",
+      "destination": "/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context"
+    },
+    {
+      "source": "/build/tools/tool-steps/knowledge/using-variables-in-json",
+      "destination": "/build/knowledge/knowledge-tool-steps#using-variables-in-json"
+    },
     {
       "source": "/use-cases/enrichment",
       "destination": "/guides/revops/getting-started"
@@ -826,6 +851,22 @@
       "source": "/templates/bulk-run",
       "destination": "/build/knowledge/enrich-with-tool"
     },
+    {
+      "source": "/build/knowledge/find-and-use-knowledge",
+      "destination": "/get-started/core-concepts/knowledge"
+    },
+    {
+      "source": "/build/knowledge/access-knowledge",
+      "destination": "/get-started/core-concepts/knowledge"
+    },
+    {
+      "source": "/build/knowledge/advanced-knowledge-retrieval",
+      "destination": "/get-started/core-concepts/knowledge"
+    },
+    {
+      "source": "/get-started/key-concepts/knowledge",
+      "destination": "/get-started/core-concepts/knowledge"
+    },
     {
       "source": "/templates/faq",
       "destination": "/get-started/core-concepts/tools"
@@ -916,7 +957,7 @@
     },
     {
       "source": "/tool/tool-steps/knowledge-search",
-      "destination": "/build/tools/tool-steps/knowledge/knowledge-search"
+      "destination": "/build/knowledge/knowledge-tool-steps#knowledge-search"
     },
     {
       "source": "/templates/sentiment-analysis",
diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 96cf5969..38995171 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -62,7 +62,7 @@ See our short guide on [best practice to prepare my CSV data](/build/knowledge/)
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 
-past response(s) to the current input. So, we need to add a [Knowledge search](/build/tools/tool-steps/knowledge/knowledge-search) component to our Tool and
+past response(s) to the current input. So, we need to add a [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) component to our Tool and
 configure the step:
 
 ![knowledge search](/images/example-use-cases/few-shot-prompt-knowledge-search.png)
diff --git a/get-started/core-concepts/knowledge.mdx b/get-started/core-concepts/knowledge.mdx
index fbfae5dc..ab5131c4 100644
--- a/get-started/core-concepts/knowledge.mdx
+++ b/get-started/core-concepts/knowledge.mdx
@@ -23,7 +23,7 @@ Think of it as your agent's reference library. When an agent needs to answer a q
     Update your knowledge bases as things change. Your agents automatically use the latest information.
   </Card>
   <Card title="Works across your stack" icon="plug">
-    Pull in data from files, websites, Google Drive, SharePoint, Notion, and more.
+    Pull in data from files, websites, Google Drive, SharePoint, Notion, Confluence, and more.
   </Card>
 </CardGroup>
 
@@ -45,6 +45,10 @@ When you add a knowledge base to an agent, you choose how the agent uses it:
 - **Add all to prompt** — the entire knowledge set is included in the prompt every time the agent runs. Best for small or simple datasets.
 - **Allow agent to search** — the agent searches the knowledge base using RAG and pulls only what's relevant. Best for large or complex datasets.
 
+### Using Knowledge in Tools
+
+You can also read from and write to Knowledge directly inside a Tool using [Knowledge Tool steps](/build/knowledge/knowledge-tool-steps) — including [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) for everyday retrieval and [Advanced knowledge search (2M context)](/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context) when you want to query your whole knowledge set with a prompt.
+
 ## Where is Knowledge most useful?
 
 Knowledge is most effective when your agents need access to specific, proprietary, or frequently changing information:
@@ -67,7 +71,7 @@ Knowledge is most effective when your agents need access to specific, proprietar
 
 <AccordionGroup>
   <Accordion title="What file types can I upload to Knowledge?">
-    You can upload CSV, PDF, Excel, JSON, and audio files. You can also pull content from websites or sync from integrations like Google Drive, SharePoint, and Notion.
+    You can upload CSV, PDF, Excel, JSON, and audio files. You can also pull content from websites or sync from integrations like Google Drive, SharePoint, Notion, and Confluence.
   </Accordion>
 
   <Accordion title="How does semantic search differ from keyword search?">
diff --git a/get-started/key-concepts/knowledge.mdx b/get-started/key-concepts/knowledge.mdx
deleted file mode 100644
index 0ad4fc9b..00000000
--- a/get-started/key-concepts/knowledge.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: 'Knowledge'
-sidebarTitle: 'Knowledge'
-description: 'Give your agents context'
----
-
-## What is Knowledge?
-
-Knowledge is our RAG solution in Relevance AI, which allows you to provide additional context and relevant information to your agents and tools.
-
-## How do I create Knowledge?
-
-Creating knowledge in Relevance AI is simple and flexible. You can:
-
-- **Manually input data** - Start with an empty table and enter information directly.
-- **Upload structured and unstructured data** - Import files such as CSV, PDF, Excel, JSON, or even audio files.
-- **Extract content from a website** - Fetch text and relevant information from URLs.
-- **Connect third-party integrations** - Sync data from external platforms.
-
-
-## Links
-On the sidebar, you have access to 
-* [Tools](/get-started/key-concepts/tools): build integrations, LLM prompt chains or other step by step automations
-* [Agents](/get-started/key-concepts/agent): reasoning bots powered by LLMs that plan and complete tasks
-* [API keys](/get-started/core-concepts/api-integration): enter your own API key(s) for the many supported vendors 
\ No newline at end of file

From 9bb982b50f517c1a1985421c4afe1971011c457e Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 10 Jun 2026 14:18:45 +1000
Subject: [PATCH 02/11] docs: tidy Knowledge Tool steps page styling and
 content

- remove the Supademo embeds from each step
- capitalize the Knowledge product noun in headings, tab titles, and prose
- wrap the step tabs in the guides' path-picker styling
- fix path-picker for this use: scroll-safe (no clip), softer non-clipped glow,
  flush symmetric edges, and a white active-tab icon (was blending into the pill)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .../integrations/knowledge-tool-steps.mdx     | 26 +++---
 build/knowledge/knowledge-tool-steps.mdx      | 82 +++++++------------
 style.css                                     | 33 +++++---
 3 files changed, 64 insertions(+), 77 deletions(-)

diff --git a/_snippets/components/integrations/knowledge-tool-steps.mdx b/_snippets/components/integrations/knowledge-tool-steps.mdx
index 2fa306cc..6baf5381 100644
--- a/_snippets/components/integrations/knowledge-tool-steps.mdx
+++ b/_snippets/components/integrations/knowledge-tool-steps.mdx
@@ -1,26 +1,26 @@
 <Columns cols={2}>
-  <Card href="/build/knowledge/knowledge-tool-steps#insert-knowledge" title="Insert knowledge">
-    Use a Tool step to insert data to your knowledge table.
+  <Card href="/build/knowledge/knowledge-tool-steps#insert-knowledge" title="Insert Knowledge">
+    Use a Tool step to insert data to your Knowledge table.
   </Card>
-  <Card href="/build/knowledge/knowledge-tool-steps#upsert-knowledge" title="Upsert knowledge">
+  <Card href="/build/knowledge/knowledge-tool-steps#upsert-knowledge" title="Upsert Knowledge">
     Use a Tool step to insert or update rows by an identifier field.
   </Card>
-  <Card href="/build/knowledge/knowledge-tool-steps#update-knowledge" title="Update knowledge">
-    Use a Tool step to update data in your knowledge table.
+  <Card href="/build/knowledge/knowledge-tool-steps#update-knowledge" title="Update Knowledge">
+    Use a Tool step to update data in your Knowledge table.
   </Card>
-  <Card href="/build/knowledge/knowledge-tool-steps#delete-knowledge" title="Delete knowledge">
-    Use a Tool step to delete data from your knowledge table.
+  <Card href="/build/knowledge/knowledge-tool-steps#delete-knowledge" title="Delete Knowledge">
+    Use a Tool step to delete data from your Knowledge table.
   </Card>
-  <Card href="/build/knowledge/knowledge-tool-steps#get-knowledge" title="Get knowledge">
-    Use a Tool step to get data from your knowledge table through search filters.
+  <Card href="/build/knowledge/knowledge-tool-steps#get-knowledge" title="Get Knowledge">
+    Use a Tool step to get data from your Knowledge table through search filters.
   </Card>
   <Card href="/build/knowledge/knowledge-tool-steps#knowledge-search" title="Knowledge search">
-    Use a Tool step to search your knowledge table.
+    Use a Tool step to search your Knowledge table.
   </Card>
-  <Card href="/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context" title="Advanced knowledge search (2m)">
-    Use a Tool step to search your knowledge table with a prompt.
+  <Card href="/build/knowledge/knowledge-tool-steps#advanced-knowledge-search-2m-context" title="Advanced Knowledge search (2m)">
+    Use a Tool step to search your Knowledge table with a prompt.
   </Card>
   <Card href="/build/knowledge/knowledge-tool-steps#using-variables-in-json" title="Using variables in JSON">
-    Reference Tool inputs and other step outputs in your knowledge JSON fields.
+    Reference Tool inputs and other step outputs in your Knowledge JSON fields.
   </Card>
 </Columns>
diff --git a/build/knowledge/knowledge-tool-steps.mdx b/build/knowledge/knowledge-tool-steps.mdx
index 99452cb9..41a8626d 100644
--- a/build/knowledge/knowledge-tool-steps.mdx
+++ b/build/knowledge/knowledge-tool-steps.mdx
@@ -3,20 +3,16 @@ title: 'Knowledge Tool steps'
 description: 'Use Tool steps to read from and write to your Knowledge tables inside a Tool'
 ---
 
-Knowledge Tool steps let a Tool read from and write to your knowledge tables. Use them to insert, upsert, update, delete, and retrieve rows, or to run semantic search over a knowledge set. Pick a step from the tabs below for its fields and examples.
+Knowledge Tool steps let a Tool read from and write to your Knowledge tables. Use them to insert, upsert, update, delete, and retrieve rows, or to run semantic search over a Knowledge set. Pick a step from the tabs below for its fields and examples.
 
-## Writing knowledge
+## Writing Knowledge
 
-These steps add, change, or remove rows in your knowledge table.
+These steps add, change, or remove rows in your Knowledge table.
 
+<div className="path-picker">
 <Tabs>
-  <Tab title="Insert knowledge" id="insert-knowledge" icon="circle-plus">
-    The Insert Knowledge step saves information by adding new rows to your knowledge table — useful for capturing and storing data dynamically as a Tool or agent runs.
-
-    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-    <iframe src="https://app.supademo.com/embed/cmcskqz8x0dx09st8u6v0t5ka" frameBorder="0" title="Add the Insert Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+  <Tab title="Insert Knowledge" id="insert-knowledge" icon="circle-plus">
+    The Insert Knowledge step saves information by adding new rows to your Knowledge table — useful for capturing and storing data dynamically as a Tool or agent runs.
 
     ### Inputs
 
@@ -58,7 +54,7 @@ Separate each object with a comma when inserting multiple rows.
     </Note>
   </Tab>
 
-  <Tab title="Upsert knowledge" id="upsert-knowledge" icon="arrows-rotate">
+  <Tab title="Upsert Knowledge" id="upsert-knowledge" icon="arrows-rotate">
     The Upsert Knowledge step inserts new rows and updates existing ones in a single step, matching on an identifier field. Use it when you're syncing data that may or may not already exist — unlike Insert Knowledge, which always adds, and Update Knowledge, which only changes rows that already match.
 
     ### Inputs
@@ -89,13 +85,8 @@ Separate each object with a comma when inserting multiple rows.
     </AccordionGroup>
   </Tab>
 
-  <Tab title="Update knowledge" id="update-knowledge" icon="pen-to-square">
-    The Update Knowledge step changes existing rows in your knowledge table, keeping your data current and accurate.
-
-    <div style={{ width:"95%",position:"relative",paddingTop:"62.5%" }}>
-    <iframe src="https://app.supademo.com/embed/cmcu7bc9z1pd69st851b05iwu" frameBorder="0" title="Add the Update Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+  <Tab title="Update Knowledge" id="update-knowledge" icon="pen-to-square">
+    The Update Knowledge step changes existing rows in your Knowledge table, keeping your data current and accurate.
 
     ### Inputs
 
@@ -170,13 +161,8 @@ Separate each object with a comma when filtering multiple rows.
     </AccordionGroup>
   </Tab>
 
-  <Tab title="Delete knowledge" id="delete-knowledge" icon="trash">
-    The Delete Knowledge step removes rows from your knowledge table, so you can keep your data relevant and up to date.
-
-    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-    <iframe src="https://app.supademo.com/embed/cmcsl75ju0e0e9st8xzau7o3z?embed_v=2" frameBorder="0" title="Add the Delete Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+  <Tab title="Delete Knowledge" id="delete-knowledge" icon="trash">
+    The Delete Knowledge step removes rows from your Knowledge table, so you can keep your data relevant and up to date.
 
     ### Inputs
 
@@ -240,19 +226,16 @@ Separate each object with a comma when filtering multiple rows.
     </AccordionGroup>
   </Tab>
 </Tabs>
+</div>
 
-## Searching and reading knowledge
+## Searching and reading Knowledge
 
 These steps retrieve rows by filter or rank them by relevance to a query.
 
+<div className="path-picker">
 <Tabs>
-  <Tab title="Get knowledge" id="get-knowledge" icon="filter">
-    The Get Knowledge step retrieves rows directly from your knowledge table using filters, without RAG. Use it when you know which rows you want rather than searching by meaning.
-
-    <div style={{ width:"90%",position:"relative",paddingTop:"75%" }}>
-    <iframe src="https://app.supademo.com/embed/cmd2oyxum341oc4kj3skjizmf" frameBorder="0" title="Add the Get Knowledge Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+  <Tab title="Get Knowledge" id="get-knowledge" icon="filter">
+    The Get Knowledge step retrieves rows directly from your Knowledge table using filters, without RAG. Use it when you know which rows you want rather than searching by meaning.
 
     ### Inputs
 
@@ -305,12 +288,7 @@ These steps retrieve rows by filter or rank them by relevance to a query.
   </Tab>
 
   <Tab title="Knowledge search" id="knowledge-search" icon="magnifying-glass">
-    The Knowledge Search step searches a knowledge table with RAG and returns the most relevant rows for a query.
-
-    <div style={{ width:"90%",position:"relative",paddingTop:"55%" }}>
-    <iframe src="https://app.supademo.com/embed/cmd7198g26fevc4kjjsus430b?embed_v=2" frameBorder="0" title="Add the Knowledge Search tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+    The Knowledge Search step searches a Knowledge table with RAG and returns the most relevant rows for a query.
 
     ### Inputs
 
@@ -322,7 +300,7 @@ These steps retrieve rows by filter or rank them by relevance to a query.
     - **Output all fields** — when on, every field is returned including the similarity score; when off, only the content field is returned.
     - **Max records to return** — the number of results to return (top k).
     - **Similarity threshold** — the minimum score a result must reach to be returned. For vector search this is cosine similarity (0–1); for keyword search it's a BM25 score (0+). Raise it for fewer, more accurate results; lower it to be more inclusive.
-    - **Use exact search** — runs exact search (good for smaller knowledge sets) when on, or faster approximate search when off.
+    - **Use exact search** — runs exact search (good for smaller Knowledge sets) when on, or faster approximate search when off.
     - **Filters** — restrict the search to a subset of rows, defined as JSON objects.
 
     With the `exact_match` filter type, pass an array to `condition_value` to match any value in it (OR semantics). A single value (`"condition_value": "x"`) matches rows where the field equals x; an array (`"condition_value": ["a", "b"]`) matches rows where the field equals a or b.
@@ -339,13 +317,8 @@ These steps retrieve rows by filter or rank them by relevance to a query.
     This filter returns results where `call_id` matches either value.
   </Tab>
 
-  <Tab title="Advanced knowledge search (2m)" id="advanced-knowledge-search-2m-context" icon="wand-magic-sparkles">
-    The Advanced Knowledge Search (2M context) step searches your knowledge table with a prompt using CAG (Cache Augmented Generation), loading your entire knowledge set into the model's long context window and generating an answer directly.
-
-    <div style={{ width:"100%",position:"relative","padding-top":"56.75%",paddingTop:"75%" }}>
-    <iframe src="https://app.supademo.com/embed/cmcwogmal1l5n9emp09x9eqv7" frameBorder="0" title="Add the Advanced Knowledge Search (2m) Tool step to your Tool" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px",objectFit:"cover" }} />
-
-    </div>
+  <Tab title="Advanced Knowledge search (2m)" id="advanced-knowledge-search-2m-context" icon="wand-magic-sparkles">
+    The Advanced Knowledge Search (2M context) step searches your Knowledge table with a prompt using CAG (Cache Augmented Generation), loading your entire Knowledge set into the model's long context window and generating an answer directly.
 
     ### Inputs
 
@@ -358,15 +331,16 @@ These steps retrieve rows by filter or rank them by relevance to a query.
     - **System prompt** — the first message that instructs the model on its role, for example expert researcher, analyst, or tutor.
     - **Temperature** — controls how creative or random the model's responses are. Lower is more focused; higher is more creative.
     - **Enable grounding** — integrates Google Search results to inform and support the model's responses.
-    - **Max documents to search** — the number of documents retrieved from the knowledge set.
+    - **Max documents to search** — the number of documents retrieved from the Knowledge set.
   </Tab>
 </Tabs>
+</div>
 
 ## Using variables in JSON
 
-When building Tools with the Insert, Upsert, Update, Get, and Delete steps, you can pass data from earlier steps or user input into your knowledge operations. Reference a Tool input with `{{input_variable_name}}` or a previous step's output with `{{steps.step_name.output.variable_name}}`, and press the **{}** button beside any JSON input field to switch it to variable mode.
+When building Tools with the Insert, Upsert, Update, Get, and Delete steps, you can pass data from earlier steps or user input into your Knowledge operations. Reference a Tool input with `{{input_variable_name}}` or a previous step's output with `{{steps.step_name.output.variable_name}}`, and press the **{}** button beside any JSON input field to switch it to variable mode.
 
-Always wrap variables in quotes — `"{{variable_name}}"`. The final type is set by the column type in your knowledge table and converted to match on insert: a value bound for a number column becomes a number even though it's quoted, a text column keeps it as text, and a boolean column stores it as a boolean. Make sure your column types match the data you're storing.
+Always wrap variables in quotes — `"{{variable_name}}"`. The final type is set by the column type in your Knowledge table and converted to match on insert: a value bound for a number column becomes a number even though it's quoted, a text column keeps it as text, and a boolean column stores it as a boolean. Make sure your column types match the data you're storing.
 
 For example:
 
@@ -425,10 +399,10 @@ For example:
   <Accordion title="What if my filters don't match any rows?">
     Nothing is deleted or returned. Make sure your filter values exactly match the data in the table, including casing and field names.
   </Accordion>
-  <Accordion title="What's the difference between Get knowledge and Knowledge search?">
-    Get knowledge retrieves rows by exact filter match, without RAG. Knowledge search ranks rows by semantic or keyword relevance to a query. Use Get knowledge when you know the exact values to match, and Knowledge search when you want the most relevant results for a question.
+  <Accordion title="What's the difference between Get Knowledge and Knowledge search?">
+    Get Knowledge retrieves rows by exact filter match, without RAG. Knowledge search ranks rows by semantic or keyword relevance to a query. Use Get Knowledge when you know the exact values to match, and Knowledge search when you want the most relevant results for a question.
   </Accordion>
-  <Accordion title="What's the difference between Knowledge search and Advanced knowledge search (2m context)?">
-    Knowledge search runs RAG retrieval and returns the most relevant rows for a query, with control over search type, filters, and thresholds. Advanced knowledge search (2m context) loads your entire knowledge set into a long-context model and answers the query directly, which suits broad questions across the whole set. Start with Knowledge search for targeted retrieval.
+  <Accordion title="What's the difference between Knowledge search and Advanced Knowledge search (2m context)?">
+    Knowledge search runs RAG retrieval and returns the most relevant rows for a query, with control over search type, filters, and thresholds. Advanced Knowledge search (2m context) loads your entire Knowledge set into a long-context model and answers the query directly, which suits broad questions across the whole set. Start with Knowledge search for targeted retrieval.
   </Accordion>
 </AccordionGroup>
diff --git a/style.css b/style.css
index 91a171c5..ff874f73 100644
--- a/style.css
+++ b/style.css
@@ -301,9 +301,9 @@ div#content-side-layout {
 /* Path-picker wrapper — frames the Tabs as one controlled unit */
 .path-picker {
   border: none;
-  border-radius: 1rem;
-  padding: 1.5rem;
-  margin: 1.5rem 0 2rem;
+  border-radius: 0.875rem;
+  padding: 1rem;
+  margin: 1rem 0 1.5rem;
   background:
     linear-gradient(135deg, rgba(79, 70, 229, 0.05), rgba(99, 102, 241, 0.02) 45%, rgba(165, 180, 252, 0.04));
   box-shadow:
@@ -323,17 +323,24 @@ div#content-side-layout {
     0 2px 4px rgba(0, 0, 0, 0.2);
 }
 
-/* In-page Tabs — pill-style buttons, centered, distinct active state */
+/* In-page Tabs — pill-style buttons, distinct active state.
+   "safe center" keeps a short tab row centered but falls back to left-aligned
+   when the row overflows, so the first/last tabs aren't clipped out of reach. */
 .path-picker [data-component-part="tabs-list"] {
-  justify-content: center;
+  justify-content: safe center;
   gap: 0.5rem;
   border-bottom: none !important;
-  padding: 0.5rem 0 1rem;
+  /* vertical padding only — gives the active button's glow room to fade inside the
+     scroll box. No horizontal padding, so the first/last tabs sit flush to the scroll
+     edges and stay symmetric when scrolled (the panel's own frame supplies the margin). */
+  padding: 0.75rem 0 1rem;
+  overflow-x: auto;
 }
 
 .path-picker [data-component-part="tab-button"] {
-  padding: 0.5rem 1.25rem !important;
-  border-radius: 0.625rem !important;
+  padding: 0.375rem 0.875rem !important;
+  border-radius: 0.5rem !important;
+  white-space: nowrap;
   border-bottom: none !important;
   margin-bottom: 0 !important;
   background-color: rgba(255, 255, 255, 0.7);
@@ -354,7 +361,7 @@ div#content-side-layout {
   color: #ffffff !important;
   box-shadow:
     0 1px 0 rgba(255, 255, 255, 0.2) inset,
-    0 4px 12px rgba(79, 70, 229, 0.35);
+    0 2px 8px rgba(79, 70, 229, 0.28);
 }
 
 .dark .path-picker [data-component-part="tab-button"] {
@@ -374,5 +381,11 @@ div#content-side-layout {
   color: #ffffff !important;
   box-shadow:
     0 1px 0 rgba(255, 255, 255, 0.15) inset,
-    0 4px 16px rgba(99, 102, 241, 0.5);
+    0 2px 10px rgba(99, 102, 241, 0.4);
+}
+
+/* Active tab icon: Mintlify paints it with the primary color (purple), which
+   disappears against our purple active pill. Force it white to match the label. */
+.path-picker [data-component-part="tab-button"][data-active="true"] .tab-icon {
+  background-color: #ffffff !important;
 }

From c14a3dddcd3fd7ab82a4782087b506eb7c2b0a77 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 10 Jun 2026 15:26:45 +1000
Subject: [PATCH 03/11] docs: address PR review comments on Knowledge pages

- Google Drive: restore the definitive 50MB file-size limit and 15-minute sync interval
- Notion: restore the definitive 5-minute sync interval
- create-knowledge: give the create flow a step-by-step feel (numbered steps, options nested)
- snippets: shorten page title to "Snippets"

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 build/knowledge/create-knowledge.mdx                  | 11 +++++++----
 .../integrated-knowledge-sources/google-drive.mdx     |  4 ++--
 .../knowledge/integrated-knowledge-sources/notion.mdx |  2 +-
 build/knowledge/use-snippets-for-quick-access.mdx     |  2 +-
 4 files changed, 11 insertions(+), 8 deletions(-)

diff --git a/build/knowledge/create-knowledge.mdx b/build/knowledge/create-knowledge.mdx
index 87ca07d9..d700e38d 100644
--- a/build/knowledge/create-knowledge.mdx
+++ b/build/knowledge/create-knowledge.mdx
@@ -23,11 +23,14 @@ This guide walks you through creating a Knowledge base and connecting it to an A
   </Card>
 </CardGroup>
 
-To create a Knowledge base, click **Knowledge** in the left sidebar, then **Create Knowledge**, and pick one of the options above.
+To create a Knowledge base:
 
-- **Empty table** — name the table and add columns (for example Question, Answer, Category), then enter rows directly.
-- **Upload files** — choose your file(s), confirm the parsing options, and name the table. Supported formats are CSV, PDF, Excel, JSON, and audio.
-- **Website** — enter the URL(s) to crawl and name the table.
+1. Click **Knowledge** in the left sidebar.
+2. Click **Create Knowledge**.
+3. Pick how you want to start, then follow its prompts:
+   - **Empty table** — name the table and add columns (for example Question, Answer, Category), then enter rows directly.
+   - **Upload files** — choose your file(s), confirm the parsing options, and name the table. Supported formats are CSV, PDF, Excel, JSON, and audio.
+   - **Website** — enter the URL(s) to crawl and name the table.
 
 ### Integrated Knowledge sources
 
diff --git a/build/knowledge/integrated-knowledge-sources/google-drive.mdx b/build/knowledge/integrated-knowledge-sources/google-drive.mdx
index e9e74c1b..556904ed 100644
--- a/build/knowledge/integrated-knowledge-sources/google-drive.mdx
+++ b/build/knowledge/integrated-knowledge-sources/google-drive.mdx
@@ -31,10 +31,10 @@ To set up Google Drive as a Knowledge source, first, open an Agent up and head t
 
 <AccordionGroup>
   <Accordion title="Is there a file size limit for Google Drive files added to Knowledge?">
-    Yes. If you select a file that's too large, you'll get an error telling you so — compress the file or pick a smaller one. If you're unsure of the current limit, [contact support](/get-started/support).
+    Yes — the limit is 50MB. If you select a file larger than that, you'll get an error telling you it's too large; compress the file or pick a smaller one.
   </Accordion>
   <Accordion title="How often do Agents fetch data from Google Drive?">
-    Connected Google Drive files sync automatically when their content changes, so your Agents reference the latest version without manual updates.
+    Connected Google Drive files sync automatically every 15 minutes, so your Agents reference the latest version without manual updates.
   </Accordion>
   <Accordion title="What should I do if my Agent fails to fetch data from Google Drive?">
     If your Agent fails to fetch data, you'll see an error notification indicating the failed fetch. You can check the specific file that caused the issue and ensure it's accessible and within the size limit. If the problem persists, try reconnecting your Google Drive or [reach out to support](/get-started/support).
diff --git a/build/knowledge/integrated-knowledge-sources/notion.mdx b/build/knowledge/integrated-knowledge-sources/notion.mdx
index b307ccd1..cafe1bb9 100644
--- a/build/knowledge/integrated-knowledge-sources/notion.mdx
+++ b/build/knowledge/integrated-knowledge-sources/notion.mdx
@@ -31,6 +31,6 @@ To set up Notion as a Knowledge source, first, open an Agent up and head to the
     Yes! You can select both Notion pages and databases as Knowledge.
   </Accordion>
   <Accordion title="How often do Agents fetch data from Notion?">
-    Connected Notion pages sync automatically when their content changes, so your Agents reference the latest version without manual updates.
+    Connected Notion pages sync automatically every 5 minutes, so your Agents reference the latest version without manual updates.
   </Accordion>
 </AccordionGroup>
\ No newline at end of file
diff --git a/build/knowledge/use-snippets-for-quick-access.mdx b/build/knowledge/use-snippets-for-quick-access.mdx
index d8f8bb53..d69d27c6 100644
--- a/build/knowledge/use-snippets-for-quick-access.mdx
+++ b/build/knowledge/use-snippets-for-quick-access.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Use Snippets for quick access'
+title: 'Snippets'
 sidebarTitle: 'Snippets'
 description: "Store reusable text once and reference it across your Tools and Agents."
 ---

From e62216632ffb31dc61a66cfe170197f4ff6cbb54 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Thu, 11 Jun 2026 13:52:54 +1000
Subject: [PATCH 04/11] =?UTF-8?q?docs:=20fix=20CI=20lint=20=E2=80=94=20FAQ?=
 =?UTF-8?q?=20heading=20and=20Supademo=20embed=20snippets?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- inactive-table-deletion: FAQ heading -> "Frequently asked questions (FAQs)"
- notion, sharepoint: replace the non-standard embed wrapper (kebab padding-top: 56.75%)
  with the standard snippet (paddingTop: '56.25%', purple border, rounded corners)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 build/knowledge/inactive-table-deletion.mdx                 | 2 +-
 build/knowledge/integrated-knowledge-sources/notion.mdx     | 5 ++---
 build/knowledge/integrated-knowledge-sources/sharepoint.mdx | 5 ++---
 3 files changed, 5 insertions(+), 7 deletions(-)

diff --git a/build/knowledge/inactive-table-deletion.mdx b/build/knowledge/inactive-table-deletion.mdx
index e6077132..3116cd67 100644
--- a/build/knowledge/inactive-table-deletion.mdx
+++ b/build/knowledge/inactive-table-deletion.mdx
@@ -43,7 +43,7 @@ If you believe you received a deletion warning in error — for example, if you
 
 ---
 
-## Frequently asked questions
+## Frequently asked questions (FAQs)
 
 <AccordionGroup>
   <Accordion title="Does this apply to Enterprise customers?">
diff --git a/build/knowledge/integrated-knowledge-sources/notion.mdx b/build/knowledge/integrated-knowledge-sources/notion.mdx
index cafe1bb9..7978857a 100644
--- a/build/knowledge/integrated-knowledge-sources/notion.mdx
+++ b/build/knowledge/integrated-knowledge-sources/notion.mdx
@@ -10,9 +10,8 @@ You can select specific Notion pages or databases for your Agent to read as Know
 
 ## Set up Notion as a Knowledge source
 
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%" }}>
-<iframe src="https://app.supademo.com/embed/cmemeidzu1jryv9kq0trvsn47" frameBorder="0" title="How to set up Notion as a source of Knowledge" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
-
+<div style={{ width: '100%', position: 'relative', paddingTop: '56.25%' }}>
+<iframe src="https://app.supademo.com/embed/cmemeidzu1jryv9kq0trvsn47" frameBorder="0" title="How to set up Notion as a source of Knowledge" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: '3px solid #5E43CE', borderRadius: '10px' }} />
 </div>
 
 To set up Notion as a Knowledge source, first, open an Agent up and head to the Build screen. Then...
diff --git a/build/knowledge/integrated-knowledge-sources/sharepoint.mdx b/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
index 91ac4162..9d36488e 100644
--- a/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
+++ b/build/knowledge/integrated-knowledge-sources/sharepoint.mdx
@@ -12,9 +12,8 @@ You can select specific Sharepoint folders or files for your Agent to read as Kn
 
 ## Set up Sharepoint as a Knowledge source
 
-<div style={{ width:"100%",position:"relative","padding-top":"56.75%" }}>
-<iframe src="https://app.supademo.com/embed/cme7vxmdp37fch3pyxzg4wb5g" frameBorder="0" title="How to set up Sharepoint as a source of Knowledge" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
-
+<div style={{ width: '100%', position: 'relative', paddingTop: '56.25%' }}>
+<iframe src="https://app.supademo.com/embed/cme7vxmdp37fch3pyxzg4wb5g" frameBorder="0" title="How to set up Sharepoint as a source of Knowledge" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position: 'absolute', top: 0, left: 0, width: '100%', height: '100%', border: '3px solid #5E43CE', borderRadius: '10px' }} />
 </div>
 
 To set up Sharepoint as a Knowledge source, first, open an Agent up and head to the Build screen. Then...

From a27b81a23b9df3cdf13bf8e4f58c991c963f6638 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:10:29 +1000
Subject: [PATCH 05/11] docs: revert edits to retired few-shot-prompting page

This page is not in docs.json (hidden/retired), so leave it untouched
and matching main rather than updating its internal link.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 38995171..96cf5969 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -62,7 +62,7 @@ See our short guide on [best practice to prepare my CSV data](/build/knowledge/)
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 
-past response(s) to the current input. So, we need to add a [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) component to our Tool and
+past response(s) to the current input. So, we need to add a [Knowledge search](/build/tools/tool-steps/knowledge/knowledge-search) component to our Tool and
 configure the step:
 
 ![knowledge search](/images/example-use-cases/few-shot-prompt-knowledge-search.png)

From 1a455aa25c40a7e0a3295ada7201c4dc70886760 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:15:14 +1000
Subject: [PATCH 06/11] docs: point few-shot-prompting knowledge link at live
 page

Avoid a redirect-dependent link on the retired page. Points straight
at the consolidated Knowledge tool steps page instead of the deleted
old path that only resolves via a docs.json redirect.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 96cf5969..38995171 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -62,7 +62,7 @@ See our short guide on [best practice to prepare my CSV data](/build/knowledge/)
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 
-past response(s) to the current input. So, we need to add a [Knowledge search](/build/tools/tool-steps/knowledge/knowledge-search) component to our Tool and
+past response(s) to the current input. So, we need to add a [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) component to our Tool and
 configure the step:
 
 ![knowledge search](/images/example-use-cases/few-shot-prompt-knowledge-search.png)

From bf88fe601cdfd141a1a87f86264cabe72d7fc90e Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:19:43 +1000
Subject: [PATCH 07/11] docs: fix broken CSV-data link in few-shot-prompting

/build/knowledge/ has no landing page (404); point at create-knowledge
to match the adjacent links.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 38995171..205ff587 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -58,7 +58,7 @@ By using a database of responses and replies that have been proven to be effecti
 
 [Upload](/build/knowledge/create-knowledge) a CSV file containing samples of received messages and your corresponding replies.
 Make sure to [enable knowledge](/build/knowledge/create-knowledge).
-See our short guide on [best practice to prepare my CSV data](/build/knowledge/).
+See our short guide on [best practice to prepare my CSV data](/build/knowledge/create-knowledge).
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 

From 74bbfd1c5926ee00e12c1a82d0fa9f69cf9e78db Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:23:58 +1000
Subject: [PATCH 08/11] docs: reword CSV link to match actual destination
 content

The link claimed "best practice to prepare my CSV data" but the target
(create-knowledge) has no CSV-prep guidance. Reword to reflect what the
page actually covers: uploading and structuring CSV data.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 205ff587..cafdbe5c 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -58,7 +58,7 @@ By using a database of responses and replies that have been proven to be effecti
 
 [Upload](/build/knowledge/create-knowledge) a CSV file containing samples of received messages and your corresponding replies.
 Make sure to [enable knowledge](/build/knowledge/create-knowledge).
-See our short guide on [best practice to prepare my CSV data](/build/knowledge/create-knowledge).
+Learn how to [upload and structure your CSV data](/build/knowledge/create-knowledge).
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 

From b7364085c931976f597ac71e7d499fec27d8ac6e Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:43:47 +1000
Subject: [PATCH 09/11] docs: revert out-of-scope few-shot-prompting edits

few-shot-prompting is a hidden page (not in docs.json) and outside this
PR's Knowledge scope. Restore it to main, undoing the earlier CSV-link
edits so this PR stays focused on the Knowledge-section consolidation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index cafdbe5c..96cf5969 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -58,11 +58,11 @@ By using a database of responses and replies that have been proven to be effecti
 
 [Upload](/build/knowledge/create-knowledge) a CSV file containing samples of received messages and your corresponding replies.
 Make sure to [enable knowledge](/build/knowledge/create-knowledge).
-Learn how to [upload and structure your CSV data](/build/knowledge/create-knowledge).
+See our short guide on [best practice to prepare my CSV data](/build/knowledge/).
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 
-past response(s) to the current input. So, we need to add a [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) component to our Tool and
+past response(s) to the current input. So, we need to add a [Knowledge search](/build/tools/tool-steps/knowledge/knowledge-search) component to our Tool and
 configure the step:
 
 ![knowledge search](/images/example-use-cases/few-shot-prompt-knowledge-search.png)

From 3d56cfff4aec4c5436cc1b557640f7f1216d2eb5 Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 15:58:42 +1000
Subject: [PATCH 10/11] docs: fix broken link on hidden few-shot page to pass
 CI link-check

few-shot-prompting is hidden (not in docs.json, no inbound links), but
the CI link-check validates all pages. /build/knowledge/ is a 404, so
repoint it to a live page. Inline comment marks why the hidden page was
touched.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 96cf5969..4ac589eb 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -58,7 +58,8 @@ By using a database of responses and replies that have been proven to be effecti
 
 [Upload](/build/knowledge/create-knowledge) a CSV file containing samples of received messages and your corresponding replies.
 Make sure to [enable knowledge](/build/knowledge/create-knowledge).
-See our short guide on [best practice to prepare my CSV data](/build/knowledge/).
+{/* Hidden/retired page (not in docs.json, no inbound links). Edited only to keep the CI link-check green: /build/knowledge/ is a 404, repointed to a live page. */}
+See our short guide on [best practice to prepare my CSV data](/build/knowledge/create-knowledge).
 
 ### 4. Search in knowledge
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 

From 89fe3a9e2175d970162654ffc41ba396ad09a2dc Mon Sep 17 00:00:00 2001
From: jordanc-relevanceai <jordan@relevanceai.com>
Date: Wed, 1 Jul 2026 16:08:10 +1000
Subject: [PATCH 11/11] docs: repoint few-shot knowledge-search link to live
 page (fix link-rot)

Mintlify link-rot ignores docs.json redirects and checks the target
page exists. This PR deletes /build/tools/tool-steps/knowledge/knowledge-search,
so the link on the hidden few-shot page was the one remaining break.
Point it at the live consolidated /build/knowledge/knowledge-tool-steps.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 example-use-cases/few-shot-prompting.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/example-use-cases/few-shot-prompting.mdx b/example-use-cases/few-shot-prompting.mdx
index 4ac589eb..9c2224cb 100644
--- a/example-use-cases/few-shot-prompting.mdx
+++ b/example-use-cases/few-shot-prompting.mdx
@@ -62,8 +62,9 @@ Make sure to [enable knowledge](/build/knowledge/create-knowledge).
 See our short guide on [best practice to prepare my CSV data](/build/knowledge/create-knowledge).
 
 ### 4. Search in knowledge
+{/* Hidden/retired page. Edited only to keep the CI link-check green: this PR deletes /build/tools/tool-steps/knowledge/knowledge-search (link-rot ignores docs.json redirects), so point at the live consolidated page. */}
 We want to create our own few-shot prompting technique based on an entire dataset. This can be achieved by using a search step to find the most similar 
-past response(s) to the current input. So, we need to add a [Knowledge search](/build/tools/tool-steps/knowledge/knowledge-search) component to our Tool and
+past response(s) to the current input. So, we need to add a [Knowledge search](/build/knowledge/knowledge-tool-steps#knowledge-search) component to our Tool and
 configure the step:
 
 ![knowledge search](/images/example-use-cases/few-shot-prompt-knowledge-search.png)