Sending Text Parameters with "Form Data" API Calls for PDFs

Need help APIs
1

Hi,

I’m trying to upload a PDF from Bubble to the Document Store in Flowise, using the API connector, and I need to include the Pinecone namespace as a text parameter to store it correctly.

I’m currently using “body-type: form data” for PDFs, and while the data reaches Pinecone, it doesn’t go to the correct namespace. See image.
I tried both “vectorStore.config.pineconeNamespace” and “pineconeNamespace” without success.

CleanShot 2025-01-08 at 10.04.41
CleanShot 2025-01-08 at 10.04.41740×537 38.3 KB

For URLs, I’m successfully sending data with “body-type: JSON” like this:

{
    "docId": "<docId>",
    
     "loader": {
        	"name": "fireCrawl",
        	"config": {
            	"url": "<url>"
    				}},
        
      "vectorStore": {
        "config": {
        "pineconeNamespace": "<nameSpace>"
        }}
}

Am I missing something for PDFs? Any advice is appreciated!

2

Try vectorStore[config][pineconeNamespace]

1 Like
3

Thanks a lot! It worked :clap:t3:

1 Like
4

@romanmg do you know if it’s possible to send more than one PDF in the same call? I’m sending only one at the time but it would be great if its possible to send more than one.

CleanShot 2025-01-09 at 12.21.46
CleanShot 2025-01-09 at 12.21.46630×518 38.8 KB

5

Based on the parameter ID being “files” (plural), I would say yes. But, you may need to change your body type to JSON instead of Form-data so you can control the parameter values with more granularity (i.e. dynamic list of files).

You’d want to put all your parameters here:

image
image1027×597 28.2 KB

Then, when you have the action in the workflow, you’ll be able to fully edit the JSON. For the “files” parameter, you can try:

“files”: [
Files URLs :formatted as text
]

And within the “formatted as text” window, you’ll see 2 multi-line windows. The first would have:

“this Files URL’s value” (something like that)

The second is for your list delimiter, so you can just type in a comma.

I’m making a few assumptions here, and I’m not sure what your “split by #join…” is all about, but this is the direction I’d try.

1 Like
6

Thanks, I’ll try this