400 when trying to override configuration of API Loader #1576
-
|
Hi Folks, My use case is a universal PDF chatbot allowing to specify the question AND the URL to a PDF in the payload. I've built a simple Railway flow where I load the PDF through an API Loader node calling APIfy with "PDF Text Extractor" actor exposed (https://apify.com/jirimoravcik/pdf-text-extractor). APIfy endpoint takes the PDF URL in the payload. It all works beautifully if I hardcode the PDF URL by clicking on "Additional Parameters" in GUI, where I can add any field to the body of the APIfy call. But: I don't want the PDF URL to be hardcoded - I want to specify it each time when calling Flowise. To do it, I need to be able to override the API Loader node configuration when doing so. I start off by removing the hard-coded "Additional Parameters" in API Loader node, and then follow Flowise's instructions to put what I need inside the body. The options for API Loader are: Now, I've tried multiple approaches to syntax (it's unclear to me from instructions), but it seems no matter which one I try, I get a 400 from Flowise. I can see Flowise never calls APIfy. Is there something I'm missing?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
@poniatowski1987 dont you have to put the urls in the body? |
Beta Was this translation helpful? Give feedback.






@poniatowski1987 dont you have to put the urls in the body?