What’s the best practice for setting up a “dynamic” knowledge base that updates from an external source?

[Ned.Malki]

Hey @michaeldsimmons long time. Nice to see you on here !

1. Pickaxe has not directly updated the system since I last responded here. However, they did ship Studio API + Make modules that can do the job!

I think a combo of the new Pickaxe Make modules + Studio API is the best workaround for the deprecated native dynamic KB feature from V1.

Knowledge base docs setup by make.com scenario?

I have a make.com scenario to create a knowledge base document based off an api key from my website. I have 2 questions about the document it’s creating. #1. The documents are being created as .txt files. Is there a way to make them create as .pdf files? #2. The new document does not automatically assign to any tool. We only have one active tool and I want the documents to automatically assign to that tool. Is there a way to set that up?

2. I recommend you connect to an Airtable database - however, since you’re using Make, both Notion and Airtable have Make modules, and since the data will be returning from Make, Pickaxe will essentially treat them the same. Does that make sense?