Guides

Knowledge

Fill your Knowledge Base, ask it questions and get answers with sources, and build agents that answer your customers from it. On every plan.

Your Knowledge Base holds what your business knows (web pages, documents, price lists, recordings) and answers questions from it, with the source of each answer. It's on every plan. Claude checks where your Knowledge Base stands first (awesomate_knowledge_status: switched on or not, this month's use against your plan), and if it isn't switched on yet, does that (awesomate_knowledge_provision).

Before Knowledge can use anything you add, you switch on Use your content for Knowledge in Settings, Features (hub.awesomate.ai/settings?tab=features). It is the second line under Knowledge: switching on Knowledge itself is not enough. Claude can't switch it on for you.

#Put things in

Add our website and our price list PDF to my Knowledge.

• Web pages and sites: awesomate_knowledge_sources adds one page or a whole sitemap.
• A whole Vimeo or Wistia library comes in from the hub, at Knowledge, Video library: you connect the library and start the import there, because it takes your provider's token and transcription is charged. Claude can then follow it for you (awesomate_knowledge_sources, video_imports): how far it has got, and which videos failed.
• Files on your computer: awesomate_knowledge_upload sends a file straight from your computer, so its contents never pass through the chat. Documents and spreadsheets work on every plan; recordings (transcribed) and images (read with OCR) on Pro and above.
• Spreadsheets go in one of two ways, and Claude asks which when it isn't obvious: as knowledge, where each row is a record people can ask about and see cited (a price list, a fee table, a timetable), or as data, for totals and trends (job or invoice history), which awesomate_knowledge_data answers from.
• Titles. An uploaded file is titled from its file name, with spaces and accented letters turned into underscores. Claude can give it a proper title afterwards (awesomate_knowledge_sources, rename). The library shows the new title straight away; answers may show the old one for a while.
• Who may see it. Each source is private, internal or public. Making something public, so anyone with a public link or chatbot can read it, is confirmed with you first. Claude can show how many sources sit at each level (awesomate_knowledge_sources, visibility_summary) and open one source with its details (get).
• When something didn't go in. Claude lists the ingest jobs (jobs) and, with your yes, tries a failed one again (job_retry). It can also tell you which video libraries are connected (video_connections).

#Files your workflows write

Keep my reports folder in my Knowledge, so I can ask about this month's reports.

If your workflows save files into your n8n's folders (Files in the hub, Support Plus and above), awesomate_knowledge_sources can keep one of those folders synced into your Knowledge: new and changed files are added within about 15 minutes, and you choose what happens when a file is removed. A folder synced as public is confirmed with you first. Claude can change a sync rule later, or switch it off (sync_rule_update). Spreadsheets in a synced folder are added only once you've said how (as knowledge or as data); until then each one is skipped, and the sync says why. One file from those folders goes in with awesomate_knowledge_upload, and a spreadsheet takes the same choice there.

#Ask it

What does my Knowledge say about refunds?

awesomate_knowledge_ask answers with numbered sources. Claude tells you when the answer didn't come from your content, rather than passing off a guess as yours. awesomate_knowledge_search shows what's in there and finds the exact page, section or moment in a video.

Who comes up most alongside our head coach?

awesomate_knowledge_people looks up a person, place or topic by name (explore), shows who and what is mentioned alongside it (related), and opens the passage behind any citation (evidence).

#Your FAQs

Pull the FAQs off our website and add them to my Knowledge.

awesomate_knowledge_faq reads FAQs from a web page (import_page), from text you paste (import_text) or from a file on your computer (import_file: a spreadsheet, Word document, PDF or text file up to 5 MB). Nothing is saved until you've seen the questions and answers and said which to keep; then Claude adds them, word for word, as drafts. It can open one set or one FAQ in full (set, entry). On Support Plus and above, it can count what your public assistants could not answer (questions_summary) and tell you whether you get the daily email about those questions, or switch it on or off when you ask (email_settings, email_settings_set).

#Number questions

How much did we invoice last quarter, by month?

awesomate_knowledge_data answers from spreadsheets you've added as data. Claude can open one dataset (dataset), rename it or settle how its columns are read (dataset_update), and look at one import (import). When an import is waiting on you, Claude can approve it, turn it away, answer its questions, run it again, or take one that's already in back out (import_action), each only after you say yes.

#Agents that answer for you

Make an agent that answers customers' questions about our services, only from our content.

awesomate_knowledge_agents builds an agent with its own instructions, the sources it may use, and how strictly it sticks to them, then publishes it. Use a strict agent for anything customers see. If you keep each business or audience in its own collection, Claude limits a new agent to the right one when it creates it, and says so when an agent it drafted would read every collection, or would skip your PDFs or FAQs. Testing a draft shows how it words things, but not what a visitor gets: the draft can quote sources a published public agent never shows. After publishing, Claude can ask the live agent as a website visitor would (visitor_test, on the plans with the public chat), and it can pause an agent and start it again (suspend, resume), each only with your yes. Claude can also manage your FAQs (awesomate_knowledge_faq), and after publishing them tells you which of your agents won't answer from them yet and why, collections of sources (awesomate_knowledge_collections) and the people and organisations your content mentions (awesomate_knowledge_people). awesomate_knowledge_data answers number questions from spreadsheets you've added. Your account's main Knowledge assistant (its persona, what it says when it can't answer, which data it may use) is read and changed with awesomate_knowledge_agent; because that assistant answers real customers, Claude shows you exactly what will change and waits for your yes.

How are my agents doing this month? Which one is the website using?

Claude can read how each agent is answering (answer_rates), the log of calls to them (logs) and which agent each website or automation uses (where_used). It can delete an agent you no longer need (delete), only after you say yes, since every website chat using it stops. It can tell you whether your own AI key is saved and which models it can use (ai_key_status, models); saving or removing the key itself is yours, in the hub at Settings, Integrations.

Put our help agent on our website.

On Support Plus and above, Claude can make a website key for a published, public agent (website_key) once you've said which sites it runs on and said yes. You get the key once, inside the code to paste before </body> on those sites. Each website key has its own monthly answer limit, by default half your account's answers when the key is made, so one busy site can't use them all. Claude tells you the number. A key's limit can't be changed later: for a different one, Claude makes a new key, you swap the code on your site, and the old key is switched off. Claude can list your website keys (website_keys) and switch one off (revoke_website_key), again only with your yes. Keys for automations and servers are made in the hub, under Knowledge, Agents.

Members should only get answers from the members' collection.

Customer groups run on access policies: a policy named segment:members (or segment:all) says what people in that group may read. Claude lists, creates, changes, pauses and removes them (policies, policy_create, policy_update, policy_suspend, policy_resume, policy_delete). A change applies to live answers at once, so Claude shows you what changes first.

Every tool is in Knowledge.