I am using Zamzar to extract pdf content. I have gotten the api calls to initialize. However, I cannot get it to run in the backend. Well at least, I see that their is no data being updated. Could someone take a look and see where the issue is?
I included as much relevant photos as possible.
I’m sorry, I can’t help with this specific API, but I was able to get PDF data extracted via API working perfectly through PDF.co
Their documentation is a bit…meh, but their support is pretty good!
Thanks for the reply. Zamzar documentation is also not as good but their support was helpful. I do not want to give up on this api just yet since I know I was able to make a call to it. I know it must be how I have the workflow set up.
Please include screenshot of API Connector settings to.
What is the content of source file? (Show arbitrary text settings)…
What do you have in logs after the calls? any error?
Here is a look at the api set up and the other stuff you asked for.
Also, I think the issue might be that the actual parameter is not being received…I think it that after some troubleshooting.
Also, how do I see the logs? Is that a bubble thing or do you mean from Zamzar end?
I am also facing this error.
okay so I went and tried PDf.co which is way easier to set up than Zamzar. Anyway, this is the error I am getting with the pdf url. Could you help?
Sorry! Did not see that you’d replied.
Unfortunately we have moved away from PDF.co, not because it wasn’t working, but because we can now get the data in CSV.
As I can’t see your entire process I’ll outline how I implemented it.
The PDF file was uploaded to AWS, the direct link to that file was then sent to PDF.co which would then parse the data using the template I created.
The results would be sent back in JSON, which I would then parse into the database.
This process was surprisingly quick and worked without issue. Looking at your error it appears that PDF.co can’t access your file via the URL you have provided?
Do you have an uploaded file URL in place to initialise the API? If not, I would suggest using a real URL from AWS.
Thanks!! I actually was able to figure it out already 
. I appreciate you still replying though.
Why was csv a better route for what you are building?
Where are you getting the JSON from?
If you’re getting it as an API response, you can simply connect each pair to the right location when you initialise the connection. With that said, I’m guessing that you don’t have that?
CSV can be parsed into the Bubble database directly (kinda) so there’s no need for the additional steps of exporting that data to a TP provider to extract it from the PDF and recieve it back as JSON.
JSON is arguably easier to deal with once you have it, as the CSV process requires plugins, but it’s simple enough once you’ve got it all hooked up! I used 1T - CSV uploader.
This topic was automatically closed after 70 days. New replies are no longer allowed.
