I’ve connected my Smartsuite with Weweb and have successfully binded most fields, but I can’t figure out how to bind the SmartSuite image field. In the one youtube video showing the integration between Smartsuite and Weweb, they show images, but dont go into how it is connected. There must be a way?
Can anyone help with this?
Also here to find the answer to this. Can anyone help? There was a video created on how to integrate Smartsuite, but no way to actually do this?
Anybody?
Hi @apeers 
To be honest, I struggle to understand SmartSuite’s API.
I created a free trial and attempted something with there “All Brand Assets” template but found it difficult to navigate.
Looking at the “LinkedIn Ads” record on here:
It looks like this here is where we can find the 14 images:
From what I understand of their API documentation (the one you referenced here), you can then fetch each image based on its handle:
This is what I did here:
Using this custom formula:
I hope that helps. If you still get stuck, I strongly suggest you reach out to SmartSuite’s support team so they can help you navigate their API.
This is amazing! Thank you so much for doing this. Seems like image url is a pretty big pain point for Smartsuite users. I’ve reached out to the Smartsuite team multiple times on this and no one has been able to provide any help, so i appreciate you taking the time to help. Thank you!
Hey @Joyce, the more i dove into this im afraid it doesn’t exactly solve the problem. In your example you are connecting only 1 record. I’m looking to get generate data for ALL records in Smartsuite.
I now see in the Smartsuite demo video here that the photos shown were not bound with a file field within Smartsuite, but rather sourced from another website.
Is this not possible yet then?
Yeah, unfortunately, I didn’t find the endpoint for this in SmartSuite’s doc. One (unsatisfying) work around would be to create a workflow in weweb with an iterator action that loops through all the records and then all the individual images to fetch each image.
A big pain for sure.
Ah I see. Yeah, their API seems to have limitations for sure, which is unfortunate. I hope they fix this in the future. Thank you for the quick response.
