Knowledge base docs setup by make.com scenario?

General
1

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?

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

Hey @brenttiesflies yes, you can do this end-to-end in Make and auto-attach the doc to your tool.

Corrected

Module 1: Your Site’s API

image
image543×959 60.6 KB

Module 2: Create Document (Pickaxe Module)

image
image615×604 38.9 KB

Failsafe Sleep Module (Optional)

image
image618×351 31.3 KB

Module 3: Connect Document - Studio API (HTTP Module)

image
image584×1205 73.6 KB

What the workflow should look like:

Screenshot 2025-09-09 034439
Screenshot 2025-09-09 0344391297×523 53.7 KB

End-to-end flow (for clarity)

  1. HTTP (Make a request) - get your site content (with API key)
  2. Pickaxe › Create Document - set Raw content of document = output of step 1
  3. (optional) Tools › Sleep - 0.5-1.5s
  4. HTTP (Make a request) - POST to …/studio/document/connect with:

Hope that helps!

~Ned

3

This is very helpful, I still have a lot to figure out but this gets me one step closer. Thanks!!!

1 Like
4

Hi, sorry, but follow-up question. Fast Path - in my Connect Document module, it will not let me map the document id from the previous Create Document module. The only option in that field is all the existing documents in my knowledge base. Am I missing something?

1 Like
5

Hey @brenttiesflies, no worries. Let me recreate from my end and update you in a moment.

6

@brenttiesflies I updated it above. I missed that the Connect Document module is not for your use case.

The difference in the corrected solution (see above) is that we’re now using an HTTP module to connect the document using the Pickaxe Studio API instead.

Let me know how it goes!

7

thanks again for your help. I set that up and it is creating the document in pickaxe but still not connecting to the specific tool. I am guessing it is because I have the wrong “pickaxeid” in the request content box? but I am not sure how to find the pickaxe id?