ancient karma
I send an image to Typebot. In Typebot I get an URL like:
https://typebot.myurl.io/api/typebots/<bunchoffstuff>
If I access this url I get the error: {"message":"Not authenticated"}
But if I access my minio, I can see that the original image URL is something like:
https://s3.myurl.io/typebot/public/workspaces/<bunchofstuff>
And that's public accessible.
How to avoid this?
(I need the public available URL to send it to GPT Vision)
ancient karma
Only happens if the image is send trough Whatsapp.
ancient karma
Web:
URL https://s3. ....
Everything fine.
Whatsapp:
URL https://paineltype. ...
"Not authenticated"
sage flame
That's right, image from WA are private by default
that's a current limitation
I need to think of a solution
ancient karma
I need to think of a solution
If I can help you with anything, please let me know.
It could be helpful if you share why things are like this, so we can think together.
And I'm open to any possible workaround to solve this, even temporarily, just so I can move forward.
ancient karma
Related to: https://github.com/baptisteArno/typebot.io/issues/1173
Do you suggest any workaround that I could use until we have an official solution?
sage flame
There are just no workaround for that... If possible, deploy the web chat for now. 🙏
This is where we parse the incoming message: https://github.com/baptisteArno/typebot.io/blob/213f69d7ea524c8f341f3c7641d390a01756de69/packages/bot-engine/whatsapp/resumeWhatsAppFlow.ts#L143-L157
This is the URL handler of the generated image link: https://github.com/baptisteArno/typebot.io/blob/213f69d7ea524c8f341f3c7641d390a01756de69/apps/builder/src/pages/api/typebots/[typebotId]/whatsapp/media/[mediaId].ts
In order to read the image stored on WhatsApp we need to be authenticated.
So I'm thinking of an additionnal option in the File upload block "Public URL" or something. And instead of parsing the URL that authenticates etc... we would automatically download the file from WhatsApp server and store it into the S3 storage for public access
ancient karma
So I'm thinking of an additionnal option in the File upload block "Public URL" o...
we would automatically download the file from WhatsApp server and store it into the S3 storage for public access
That sounds ideal. However, since we are currently utilizing only the Text Block, I believe the corresponding option should be integrated into the WhatsApp integration rather than the File Upload block.
Alternatively, we might consider omitting the need for an option altogether and simply implementing this automatically.
Every file sent to the bot could be seamlessly stored in its S3 storage, regardless of its source.
sage flame
That'd be sad to store files in 2 different storages WhatsApp + S3
ancient karma
That'd be sad to store files in 2 different storages WhatsApp + S3
Not as sad as not being able to use the image. 😆
But I got your point.
sage flame
It will make sense to add the option to set the uploaded file private or public in the block settings.
Will work on that fairly soon 🙏
ancient karma
Will work on that fairly soon 🙏
Thank you! 🙏
In the meantime, I'll try to find a workaround so I don't have to put the project on hold again.
ancient karma
Anyone able to help me?
sage flame
I'll take a look in a few minutes
ancient karma
@sage flame I saw you added the visibility to the FileUpload.
Can I use this somehow to solve my problem, where what I'm using is a Text Input (cause I don't know if the user will send a text or a file)?
ancient karma
Whatsapp:
URL `https://paineltype. ...`
"Not authenticated"
☝️
ancient karma
set to Public and you should be good to go
Where?
I'm not using the FileUpload block.
I was kinda of expecting something here:
My flow uses Text Block
In the previous version, when I sent a FileUpload through WhatsApp and collected it with the TextBlock, I used to receive a private URL to the image, as show on the print screen. (I never utilized the FileUploadBlock for this)
In the current version, the same flow now returns an "invalid message" error.
This puts me in a worse situation than before. 😆
ancient karma
Ok, but....
If I use FileUpload block, user can't send text messages. Right?
sage flame
Right!
So you need an input where the user can either send a text message or a file?
Can't you just know if you need a file or text before hand?
ancient karma
I had one. Text input.
it used to work for both (except by the fact that the URL was private).
Look at my old print:
It's a Text Block.
sage flame
Yes but it should not work
That was an issue
If you collect a text input, you shouldn't allow collecting an image
that would not make sense
On your flow, it looks like you are clearly asking for an image
Why don't you add a File input block?
That is meant for that 😅
ancient karma
To my flow to work the user is supposed to be able send text and/or image.
ancient karma
Ok, thank you for everything.
I'll have go back to the last version (where the Text Block used to accept file uploads) and try to bypass the private URL.