Pipeline Bucket - Can it be used to accept files from API calls?

Question

Hello fellow Quickbasers!I am using an image processing API to compress and resize images before uploading to Quickbase. I have _most_ of it working using a FetchJSON pipeline step .. the original image goes out, and I get the correct response back from the image processing service.&nbsp;The next step escapes me though -- the result is not an application/json content type, it's an image/jpg result. EG the below.
HTTP/1.1 200 OK
Compression-Count: 1
Image-Width: 530
Image-Height: 300
Content-Type: image/jpeg
Content-Length: 46480

[binary]
With just pipelines, not codepages, has anyone been able to process a result like this? The Iterate over JSON step doesn't seem to work because there's no JSON schema to reference (and it's the wrong content type) .. I'm thinking&nbsp;maybe a bucket step would work?Thanks in advance!M&nbsp;------------------------------Malcolm McDonald------------------------------

doughenning1 · Answer

The "Fetch JSON" channel expects the return value to be JSON, but your returned data is an image so it's not the right channel in this instance. Instead, use "Make a Request" under "Webhooks". Then you can reference the image data using the "content" property (e.g. {{a.content}}).

Hope this helps!

------------------------------
Doug Henning
------------------------------

malcolmmcdonald · Answer

Thanks Doug-- that does get me further -- I can now "see" the image binary in the pipeline's output - but still can't do much with it.

Intention is for the file to be uploaded as a file attachment .. but that pipeline only accepts a URL. I tried it anyways, and it didn't take the binary. I'm stuck feeling like buckets might be an approach (limited documentation but it talks about handling files?). Ideally I'm not setting up a box account or something as a temporary URL hosting.. seems like too many steps in the chain.

Any other thoughts?? Thanks again for your help!

M

------------------------------
Malcolm McDonald
------------------------------

doughenning1 · Answer

Hey Malcolm,&nbsp;
You can use the records upsert API to upload attachments:https://developer.quickbase.com/operation/upsertThis page about file types shows that the attachment file data needs to be Base64 encoded:https://developer.quickbase.com/fieldInfoSo for you in Pipelines, you could do this:
{
  "value": {
    "fileName": "report.pdf",
    "data": "{{a.content | base64_encode}}"
  }
}
Hope that helps!------------------------------Doug Henning------------------------------

malcolmmcdonald · Answer

Doug -- thank you for continuing to work this very much appreciated. I've engaged QB Support too .. I think we're an inch from the finish line, but stuck at the binary encoding part. The jinja filter | base64_encode can only handle string, but the image mime-type encoding (I think I'm saying that right) has all kinds of characters outside of the 128-ascii set expected.Annoying because the source image manipulation service API won't return a url I can just download the file from, and annoying because QB doesn't accept the result it without me finding another API to do the conversion step. I can see all kinds of local server-side solutions in javascript etc, but nothing I can fire off in pipelines.If I come to a solution, I'll post here -- and thank you!M------------------------------Malcolm McDonald------------------------------

Forum Discussion

Pipeline Bucket - Can it be used to accept files from API calls?