Hello,
I am new to Velo and would like your opinion on this project:
My client is a property agent (sale and rent), they create their listings in Alto Software CRM and it is automatically synchronised to Zoopla and Rightmove, I need to do the same with their WIx website.
I was told to look at Velo and these are my conclusions, maybe you can give kind advice if I am in the right direction:
1) I created a collection and associated repeaters in Wix, they look fine. Each repeater contains an image and some text field.
2) Now I need to create a details page (clicking the image) and show an image gallery, for that I need to create an image database and connect it to the property as explained in
https://www.youtube.com/watch?v=0Y4Kv5faPsY 4:45
3) Now to the Velo part: I need to interrogate the Alto API ( I got it) and hope to get all images and information.
I will start a backend job (jobs_config) every day to sync to Alto. I have to delete all collections and query Alto to build everything from scratch. I can't see another way to sync (push or pull) - any idea?
4) I will use Secret manager and get.secret() to store and use Alto API Keys. Then use .fetch to query the API like in https://dev.wix.com/docs/velo/articles/getting-started/integration-with-third-party-services
5) Use wixdata.insert() to build the collections. I am not sure how images and image gallery from API will be saved as files:
https://dev.wix.com/docs/velo/articles/getting-started/give-get-example-integrating-with-third-party-services only shows text information,
6) Then use .importFile() to import image files and build the collections accordingly.
Do you think this makes sense or am I missing something?
Thank you so much for reading my post and if you can provide your inputs.
Denis
Hello Eitan, Thanks very much for your reply and the heads-up, very appreciated.
D
Hi Denis, Thanks for your question. I have two insights which may help you: 1. You don't necessarily need to store the data in a Wix CMS Collection to display it on your site. You can fetch the data from the API directly when needed and utilize Wix Routers to create pages for each entry.
2. If you do decide to store the data in a Wix Collection, you may be able to utilize webhooks provided by the third party API to update the collection when new data is added instead of utilizing scheduled jobs (this depends on what the third party makes available). 3. Regarding images - it may be easier to store a reference to the image (i.e url) instead of storing the actual image on Wix. This saves you the trouble of importing the images and hitting storage limits in Wix. Otherwise you seem to have the general approach right. Best of luck,
Eitan