Knowledge base

Search the business's own notes and uploaded documents (PDF, Word, CSV, text, Markdown, JSON, XML).

What it does

Searches the project's own facts and uploaded documents. This is what stops an agent inventing answers: give it the price list, the policies and the FAQs, and tell it to answer only from them.

What you need

No key and no account. Put the facts in first: open Settings on this project and write them into the Knowledge base, or upload documents there. Then tick this tool on any agent that should use it.

Connecting it

Nothing to connect. It is available to every project already — tick it on an agent, or choose it in an Action step.

Using it in a step

An Action step runs one tool with the arguments you type, exactly as written, with no model involved — so it costs nothing per run and behaves the same every time. Add one from the canvas toolbar, choose Knowledge base, and fill in:

Field	Required	What goes in it
`query`	yes	What to look for in this project's own facts and documents.

Values can carry results forward: {{previous}} is the step before, and {{row:column}} is a column from the row this run is about when the trigger fans out.

Press Try it to run the step on its own before committing to a whole sequence.

Using it with an agent

Tick Knowledge base on any agent that should be able to call it, and the agent decides when to. Use an agent when the judgement matters and an Action step when the certainty does.

A worked example

A support agent answers 'do you deliver to Enugu?' from the business's actual delivery policy, uploaded as a PDF, rather than from a plausible guess.

When it goes wrong

It answers with nothing. The knowledge base is empty until somebody fills it. Open project Settings and add the facts or upload the documents first.