Data in and out
Pimberly
Bring your product records out of Pimberly into the Kabaido catalogue on a scheduled pull or as a file.
Where it stands today
Template
A prepared recipe on a generic path, which you finish.
- What you get
- Let Pimberly stay the place product data is edited, and keep the Kabaido catalogue the same records without anyone maintaining two.
- What moves
- In: products, their attributes and their media references, on the schedule you set or when you import the file. Out: nothing. Kabaido does not write back into Pimberly.
- What you hand over
- A read credential from your own Pimberly account, or simply the exported file. Kabaido holds a credential encrypted and never shows it again.
Set it up
- 1Export or expose the channel you want from Pimberly, as an API endpoint or a file.
- 2Create the catalogue connection here with that endpoint and your own credential, or start a file import.
- 3Map the fields onto your schema, run the dry run and read the validation report.
- 4Schedule the pull, then re run it whenever the schema changes.