Public Image URL

[melissa]

Hello,

I’m using an API that requires a public image URL. I’d like to acquire public URLs for the images I upload in Triggre to use them with the API. Is this possible?

Thank you in advance,
Melissa

[Jochem]

Hi Melissa,

Yes that is possible. Although you need a bit of a workaround.
The url that you get from the public image should be converted to a picture.
You can do that by calling “an incoming API”

So,
You receive the url from the API, like:
“images”: [
{
“id”: 792,
“src”: “https://example.com/wp-content/uploads/2017/03/test.jpg”,
},

Then call a connection Triggre in your application named:
“Convert url to picture”
Input: id (number, id in example), file (url, src in example)
Create flowpart “Convert url to picture” and add picture to id

Important:
Format url in request as { “Url”: “https://some.image”}

Attached an example application where this is done.
Save convert to picture version.triggre (1.5 MB)

[melissa]

Hi Jochem,

Thanks for your response! However, this is not exactly what I meant. In Triggre, I want to be able to upload an image and receive a public URL for it that I can include in an API.

Melissa

[Jochem]

Hi Melissa,

Allright, I know what you mean. Good question. I will come back to that!

[ronald]

Curious for a solution!

[Jesse]

Hi @melissa,

Currently we don’t support publicly available images; the reason is that this would be a security breach. If any image that is available in your Triggre application would be public, that could lead to problematic situations.

We are working on ways that you can use stored images and files using the Web API, which would open up different solutions (that are more elegant than what I have come up with for now). Whether we will support completely public images such as for your case, is not sure yet. It depends on whether we can handle the security risks in a simple, transparent way for you as a designer.

Solution
That being said, I might have found a workaround. You can use Dropbox to store images for free, using Zapier. These are then publicly available (through the Dropbox ‘Share link’), and you can store this URL in Triggre. Here’s how to create such a solution:

1. Create a data item named Public image that stores the files you want have publicly available. Give it an Image property, a Number sequence (name this one ‘ID’) and a URL property. The URL will store the publicly available link and the number is used to identify the item.

2. Add a flow part named Store URL for public image. Add a URL and a Number (this is the ‘ID’ for the item) as input.

3. Now add a Look up action, that searches for the Public image item with the ID from the input. There will always only be one such item, since each item gets a unique number automatically.

4. After the look up action, add an Edit action and store the URL from the input in the data item you looked up. End the flow part.

5. Create an automation flow named Store public image URL, with a URL and a Number (this is the ‘ID’ for the item) as input (same as for the flow part you created).

6. Add the created flow part named Store URL for public image to your automation flow, and supply the ID and URL as inputs. End the automation flow after this flow part.

7. Publish your application and create a Public image item. (You need an extra user flow to do this, which can be created automatically. All it needs to do is store the image in the data item.)

8. In Zapier, create a Zap that starts when a new Public image is created.

9. Add a Dropbox step to this Zap, to store the file.

10. Add a Triggre action to your Zap, that starts an automation flow. Choose the Store public image URL automation flow. As inputs, supply the ID you got from the start of the Zap, and as the URL use the Share link from the Dropbox action.

Result
When you add a Public image by uploading an image in your application, the Zap will be triggered and upload the image to Dropbox. Then it will send back the URL for the image that you can use publicly, back to Triggre and store it in the item.

I haven’t created the application as I described it here, so there might be a small error in my thinking. However, this solution should work and I hope that this is a solution for your case.

[melissa]

Hi Jesse,
Thanks for your response. We’ve successfully resolved the issue by utilizing Zapier as well.

Kind regards,
Melissa Barneveld.

[Jesse]

Hi @melissa,

Great to hear that you have found a solution. I hope our considerations regarding security were clear. It is a topic we take extremely seriously due to the nature of data some customers store in their Triggre applications.

If there are any tips regarding the solution you created, that may also benefit others, please share them in this thread.

Good luck on building the rest of your solution!

[Jochem]

Hi @melissa,

Jesse was faster than to respond and I also see that you already came up with a solution.
But I still want to share my solution with Zapier:

I simply connect Triggre with Triggre.
So, when I add a new record to a table (step 1)
Then I want connect to the created flow “Receive file” in my example (step 2).
The flow has two inputs: file (file) and url (url) which update the file.

Then I use the file from Triggre as an input for the url.

After this, the file is converted from file to public url.

[ronald]

In the new version of the Zapier connection, the solution Jochem provided does not seem to work anymore.

After 1+ year, is there another way to send images to an external service, in this case Duda?

[Jochem]

Hi Ronald,

Since we have updated Zapier this works a bit different but still you can use zapier to send this file. You can create a zap in Triggre and use this zap to send this file.

Till this date there is no other way to send images.