Pretty sure this should be easy: Trouble adding PDF-to-Text response to Bubble database

[cmarchan]

Thanks … and how does the body text looks? Does it have weird characters perhaps?

[paul36]

Not beyond what you’d expect in a json text output. As you can see, it’s got “/n/“ for line breaks, etc.

[cmarchan]

This may be breaking the OAI call as the JSON needs to be escaped.

Use the operator JSON-SAFE to escape it. When using this operator make sure not to add quotes to the API connector variable for that body

[paul36]

Thanks! Just tried it. Nothing seems to have changed. The reinitialization call went through, but the database “Offer_Text” field is still unpopulated. Confirming, you meant that the Header “content-type” parameter on the outgoing call to Chat should be “json-safe” as below, right?

Also, When I removed the quotes from around the “content,” it returns an error (below). So I left the quotes around the “content” text in the call. I haven’t added any quotes.

Let me know if I’m misunderstanding something in your idea.

(Here’s the error I get when I remove the quotes from the “content”

[paul36]

Out of savage curiosity, I changed the PDF.co parameter to “json-safe.” no change there either.

[paul36]

Progress! (I think.)

When I set the Workflow operator going into Chat as just the “body” but set the output to the “Offer_Text” field in the database as the “body” as “JSON-safe,” the field is populated by just empty quotation marks, like this:

So something is being sent to the “Offer_Text” field, just not the “body” text.

Do you have any ideas as to how I can get the text to populate there?

FYI, here are screenshots of the workflow operator entries (1) going into Chat and (2) attempting to populate the “Offer_Text” field:

1. Workflow operator going into Chat (just "body):
   

   

2. Workflow operator command to populate “Offer_Text” field (with “JSON-safe”):
   

[paul36]

BTW, when I formatted the “Result of step 1’s body” going into Chat as “JSON-safe,” It returned an error that it was not received a formatted valid JSON input. Here’s the error:

[cmarchan]

The header content-type for OAI should be application/json. I did not indicate anything about the header of the api call.

Good to hear that you are escaping json better.

[paul36]

Right! Your idea got me futzing with the formats going in and coming out of PDF.co and Chat, which got those empty quotation marks.

Thanks so much again for your help on this.

And Happy New Year!

[paul36]

Say, do you have any thoughts about how I can just get the results of the PDF-to-Text API “body” results to load into my Bubble database? Just that simple step I think might get me on my way.

[cmarchan]

I may have suggested in some fashion what I list below:

• Set the api call.
• Use it in an empty page with just one button to trigger it, retrieve the answer by displaying it onto a text element. This will let us know if the body is being returned.